legacy mode, the guest graphics
> > + * driver may attempt to use stolen memory, however only legacy
> mode
> > + * has BIOS support for reserving stolen memory in the guest VM.
> > + * Emulate the GMCH register in all cases and zero out the stolen
> > +
> > On 26 Jul 2017, at 08:22 AM, Zhang, Xiong Y <xiong.y.zh...@intel.com>
> wrote:
> >
> > Sorry, we indeed found Intel windows guest graphic driver couldn't be bind
> when GMS memory size is zero. And we have fixed it and the next intel
> windows driver rele
driver allocate extra ~4G memory when GMS size set
to 0 ?
thanks
> -Original Message-
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Tuesday, July 25, 2017 11:32 PM
> To: Dmitry Fleytman <dmi...@daynix.com>
> Cc: qemu-devel@nongnu.org; Zhang
> On Fri, 31 Mar 2017 19:03:49 +0200
> Igor Mammedov <imamm...@redhat.com> wrote:
>
> > On Thu, 30 Mar 2017 20:55:11 -0600
> > Alex Williamson <alex.william...@redhat.com> wrote:
> >
> > > On Fri, 31 Mar 2017 02:27:11 +
> &
> On Fri, 31 Mar 2017 02:27:11 +
> "Zhang, Xiong Y" <xiong.y.zh...@intel.com> wrote:
>
> > > On Thu, 30 Mar 2017 18:27:21 +0800
> > > Xiong Zhang <xiong.y.zh...@intel.com> wrote:
> > >
> > > > This reverts commit c2b2e1
s mean that legacy mode IGD assignment is not going to work
> on Gen9+ with Windows? Will it continue to work with Gen8-?
[Zhang, Xiong Y] I try to use the following qemu command to enable legacy mode
on SKyLake, but It seems the entry point of wins IGD driver isn't called(I
couldn't confirm this as
set dependencies of IGD such that it could be assigned as just
> another PCI device? Does this mean that the drivers fail to meet that
> promise by evaluating the size and location of stolen memory as
> programmed on the physical device even in UPT mode?
[Zhang, Xiong Y] The intent of
Zhang, Xiong Y would like to recall the message, "[Qemu-devel] [PATCH]
vfio/pci-quirks.c: Disable stolen memory for igd VFIO".
hipset dependencies of IGD such that it could be assigned as just
> another PCI device? Does this mean that the drivers fail to meet that
> promise by evaluating the size and location of stolen memory as
> programmed on the physical device even in UPT mode?
[Zhang, Xiong Y] The intent
