Hi,
> >
> > Completely different thing crossing my mind: I think we can make
> > virtio-vga fully compatible with stdvga. stdvga has two bars, memory
> > (#0) and mmio (#2). We can make the mmio bar larger and place all the
> > virtio regions there.
> >
>
> Full compatibility with some
Hi,
Completely different thing crossing my mind: I think we can make
virtio-vga fully compatible with stdvga. stdvga has two bars, memory
(#0) and mmio (#2). We can make the mmio bar larger and place all the
virtio regions there.
Full compatibility with some standard sounds
On Thu, Mar 26, 2015 at 04:07:16PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > 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.
> >
> >
Hi,
> 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
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
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
On Thu, Mar 26, 2015 at 09:42:47AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > And is it possible to use offset within BAR and/or memory BARs?
> > If yes I'd strongly prefer this.
>
> What is the point? Do you want place virtio regions and vga framebuffer
> in the same pci bar? Why? virtio is
Hi,
> And is it possible to use offset within BAR and/or memory BARs?
> If yes I'd strongly prefer this.
What is the point? Do you want place virtio regions and vga framebuffer
in the same pci bar? Why? virtio is mmio and traps into qemu on
access, whereas the vga framebuffer is
Hi,
And is it possible to use offset within BAR and/or memory BARs?
If yes I'd strongly prefer this.
What is the point? Do you want place virtio regions and vga framebuffer
in the same pci bar? Why? virtio is mmio and traps into qemu on
access, whereas the vga framebuffer is memory-backed
On Thu, Mar 26, 2015 at 09:42:47AM +0100, Gerd Hoffmann wrote:
Hi,
And is it possible to use offset within BAR and/or memory BARs?
If yes I'd strongly prefer this.
What is the point? Do you want place virtio regions and vga framebuffer
in the same pci bar? Why? virtio is mmio and
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
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
On Thu, Mar 26, 2015 at 04:07:16PM +0100, Gerd Hoffmann wrote:
Hi,
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
Hi,
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
14 matches
Mail list logo
