Hi,
> Option 2: QEMU provides the emulated display refresh event to the
> vgpus provided by vendor driver. For vgpus, the display refresh event
> can be considered as the vblank event which is leveraged by guest
> window manager to do the plane update or mode-setting.
> People are asking if
> > > +#define VFIO_IRQ_TYPE_GFX(1)
> > > +/*
> > > + * vGPU vendor sub-type
> > > + * vGPU device display related interrupts e.g. vblank/pageflip */
> > > +#define VFIO_IRQ_SUBTYPE_GFX_DISPLAY_IRQ (1)
> >
> > If this is a GFX/DISPLAY IRQ, why are we
Hi,
> > > Couldn't you expose this as another capability within the IRQ_INFO return
> > > data? If you were to define it as a macro, I assume that means it would
> > > be
> > > hard coded, in which case this probably becomes an Intel specific IRQ,
> > > rather
> > > than what appears to be
Hi,
> > Really need to split for different planes? I'd like a
> > VFIO_IRQ_SUBTYPE_GFX_DISPLAY_EVENT
> > so user space can probe change for all.
> User space can choose to user different handlers according to the
> specific event. For example, user space might not want to handle every
> cursor
On Thu, Feb 21, 2019 at 10:44:06AM -0800, Alistair Francis wrote:
> On Thu, Feb 21, 2019 at 3:52 AM kra...@redhat.com wrote:
> >
> > On Thu, Feb 21, 2019 at 12:33:03AM +, Alistair Francis wrote:
> > > When running RISC-V QEMU with the Bochs device attached
On Thu, Feb 21, 2019 at 12:33:03AM +, Alistair Francis wrote:
> When running RISC-V QEMU with the Bochs device attached via PCIe the
> probe of the Bochs device fails with:
> [drm:bochs_hw_init] *ERROR* ID mismatch
>
> This was introduced by this commit:
> 7780eb9ce8 bochs: convert to
6 matches
Mail list logo
