On Fri, Jan 23, 2015 at 03:48:28PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > > Also seabios wouldn't map the bar
> > > above 4G.
>
> > We can teach it to do that, and even if not, OS can do it on hotplug.
>
> Just to clarify: seabios can do it in the general case, it just wouldn't
> do it for x
Hi,
> > Also seabios wouldn't map the bar
> > above 4G.
> We can teach it to do that, and even if not, OS can do it on hotplug.
Just to clarify: seabios can do it in the general case, it just wouldn't
do it for xhci specifically because otherwise the seabios xhci driver
wouldn't be able to re
On Fri, Jan 23, 2015 at 02:53:27PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > I wanted to make the modern BAR prefetcheable, so it can
> > be a full 64-bit one,
>
> It's not the case right now though, the two bars have identical
> attributes, and there is plenty of unused space in the modern virti
Hi,
> I wanted to make the modern BAR prefetcheable, so it can
> be a full 64-bit one,
It's not the case right now though, the two bars have identical
attributes, and there is plenty of unused space in the modern virtio
bar ...
> this is impossible with the MSI-X
> BAR.
What exactly is imposs
On Fri, Jan 23, 2015 at 01:29:43PM +0100, Gerd Hoffmann wrote:
> Only for legacy-free virtio devices, to avoid unpleasent
> surprises with old drivers.
>
> mtree snippet:
>
> fea0-fea7 (prio 1, RW): virtio-pci
> fea0-fea00fff (prio 0, RW): vir
Only for legacy-free virtio devices, to avoid unpleasent
surprises with old drivers.
mtree snippet:
fea0-fea7 (prio 1, RW): virtio-pci
fea0-fea00fff (prio 0, RW): virtio-pci-common
fea01000-fea01fff (prio 0, RW): virtio-p
