On Thu, Mar 21, 2013 at 10:54:31AM -0700, H. Peter Anvin wrote: > On 03/21/2013 10:49 AM, Michael S. Tsirkin wrote: > > > > Just to clarify, I expect BIOS to use it *for config access*. > > Notification will support IO anyway because it's > > faster on KVM, so BIOS can use it directly. > > > > Ah, yes, of course. > > Quite frankly, I don't see any reason to support *anything else* for > configuration, does anyone else? > > I thought we were talking about the doorbell/notification/kicker > register. For I/O space especially it is highly desirable if that can > be in a minimal BAR (4 bytes). > > -hpa Not necessarily a BAR. We have trouble allocating IO BARs. What I want to allow is hypervisor which allocates a fixed address/data pair in the hypervisor, reserves it in ACPI and reports to driver through a vendor specific capability. You likely didn't see this discussion, it was only sent to kvm and virtualization lists, the subject is 'virtio PCI on KVM without IO BARs' -- MST _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
