On Thu, Mar 26, 2015 at 12:38:43PM +0100, Gerd Hoffmann wrote: > Hi, > > > Absolutely, it's pretty common to mix regions in a BAR. > > For example, we have virtio kick (ioeventfd backed, > > handled in kernel) in same BAR as common and device > > specific configuration. > > > We did the same thing you are now doing with the > > virtio BAR, and now we have to maintain two code > > bases, virtio pci config was designed to be future proof > > so why not use it? > > It's not about virtio at all. It's about vga compatibility, so we have > a simple framebuffer as boot display. Only used when virtio is *not* > enabled. > I don't know. This seems exactly like the kind of thing we had in mind when we added the virtio pci capability. For example, we have text in spec that requires drivers to skip unknown capabilities. And yes, if bios pokes at a specific bar then we do need to list this info in the virtio spec so this makes it an issue that is virtio related. > > This is mostly just making sure we don't paint ourselves into a corner. > > It's a simple memory bar. vga cards have that since pci was invented > (standalone ones, chipset graphics aside), and there havn't been > fundamental changes ... > > cheers, > Gerd > Yes, it's not about what we put there now. It's about being able to move things about in the future without breaking guests. -- MST _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
