User Details
- User Since
- Aug 27 2020, 6:07 AM (256 w, 6 d)
Mon, Jul 28
Setting every single cpuid value seems to be a bunch of work for user. Especially, as user have to set every single bit correctly. What's the way forward for this? How will bhyve receive some default cpuid values?
This should be merged into the previous commit D51552 shouldn't it?
Could you please describe a use case in the commit message?
Jun 27 2025
- rename len to size to match common naming in pci_passthru.c
- use uint64_t instead of vm_* types
- account for new handler interface (including baridx)
- use uint64_t instead of vm_* types
- use uint64_t types instead of vm_* types
- add baridx parameter to read/write handler
- this parameter can be used in the future to e.g. add a generic PCI config mirror in BAR space which is quite common according to QEMU [1]
- fix build
Jun 24 2025
- fix style issue
- use correct offset for 64 bit BDSM read/writes
- fix style issues
- make use of trunc_page and round_page
- fix style issues
- make global variables const
Jun 17 2025
Jun 12 2025
- rebase onto main
- rebase onto main
- rebase onto main
- rebase onto main
- make use of igd_ops
- rebase onto main
May 19 2025
May 6 2025
Feb 4 2025
Jan 21 2025
Jan 20 2025
Any comments on this?
Any comments on this?
Jan 6 2025
Nov 12 2024
Oct 22 2024
Sep 20 2024
Sep 18 2024
Where's the commit message?
It would be a very good idea to improve your commit message. It would be nice to explain the use case in more detail (if possible). Additionally, it would be great to mention limitations of this new feature e.g. that user have to make sure to protect the tcp socket from unprivileged access.
ping
ping
ping
ping
Sep 9 2024
Please add a commit message.
Sep 2 2024
Is this ready? So far, LGTM.
Aug 29 2024
Aug 28 2024
Aug 26 2024
Aug 23 2024
Aug 22 2024
LGTM. Will test it.
Aug 21 2024
Aug 14 2024
Aug 12 2024
Aug 9 2024
- avoid code duplication by moving the code below element insertion
Aug 8 2024
- use a new top level case to detect empty entries