I would say let it be undefined... in most cases the host will know what device(s) will matter; e.g. if the guest is ppc no point in providing an I/O BAR.
Rusty Russell <[email protected]> wrote: >"Michael S. Tsirkin" <[email protected]> writes: >> On Mon, Mar 25, 2013 at 08:30:28PM +1030, Rusty Russell wrote: >>> Let's go back a level. Do we still need I/O bars at all now? Or >can we >>> say "if you want hundreds of vqs, use mem bars"? >>> >>> hpa wanted the option to have either, but do we still want that? >> >> hpa says having both is required for BIOS, not just for speed with >KVM. > >OK so the offset must not be applied to the I/O bar as you suggested. > >Since AFAICT I/O bars are deprecated, should we insist that there be a >memory bar, and the I/O bar is optional? Or just leave it entirely >undefined, and say there can be either or both? > >I dislike the idea of BIOS code which assumed an I/O bar and thus won't >work with a compliant device which doesn't provide one. I'd prefer all >compliant drivers to work with all compliant devices. > >Cheers, >Rusty. -- Sent from my mobile phone. Please excuse brevity and lack of formatting. _______________________________________________ Virtualization mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/virtualization
