From: Alex Williamson <alex.williamson@redhat.com>
To: "Corvin Köhne" <C.Koehne@beckhoff.com>
Cc: "tomitamoeko@gmail.com" <tomitamoeko@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"clg@redhat.com" <clg@redhat.com>
Subject: Re: [PATCH v2 9/9] vfio/igd: add x-igd-gms option back to set DSM region size for guest
Date: Wed, 4 Dec 2024 15:35:28 -0700 [thread overview]
Message-ID: <20241204153528.5059341e.alex.williamson@redhat.com> (raw)
In-Reply-To: <fb3afcb5ea495e96c6aa9e657cb413ab47c15026.camel@beckhoff.com>
On Tue, 3 Dec 2024 16:30:56 +0000
Corvin Köhne <C.Koehne@beckhoff.com> wrote:
> On Tue, 2024-12-03 at 21:35 +0800, Tomita Moeko wrote:
> > CAUTION: External Email!!
> > DSM region is likely to store framebuffer in Windows, a small DSM
> > region may cause display issues (e.g. half of the screen is black).
> > By default, QEMU uses host's original value, which is determined by
> > DVMT Pre-Allocated option in Intel FSP of host bios. Some vendors
> > do not expose this config item to users. In such cases, x-igd-gms
> > option can be used to manually set the data stolen memory size for
> > guest.
> >
> > When DVMT Pre-Allocated option is available in host BIOS, user should
> > set DSM region size there instead of using x-igd-gms option.
> >
>
> It might be worth linking the commit which has removed x-igd-gms and mention
> that the behaviour changed slightly. Previously, the DSM region size was set to
> 0 if x-igd-gms was unset. This patch keeps the host value if x-igd-gms is unset.
Yes, this is really quite confusing. We never actually removed the
x-igd-gms option as $Subject implies, we only gutted it from doing
anything, *sigh*. Let's please summarize how 971ca22f041b left the
option but removed any implementation behind that option and this
brings it back to provide some function.
> > Signed-off-by: Tomita Moeko <tomitamoeko@gmail.com>
> > ---
> > hw/vfio/igd.c | 17 +++++++++++++++++
> > 1 file changed, 17 insertions(+)
> >
> > diff --git a/hw/vfio/igd.c b/hw/vfio/igd.c
> > index e464cd6949..0814730f40 100644
> > --- a/hw/vfio/igd.c
> > +++ b/hw/vfio/igd.c
> > @@ -717,6 +717,23 @@ void vfio_probe_igd_bar4_quirk(VFIOPCIDevice *vdev, int
> > nr)
> >
> > QLIST_INSERT_HEAD(&vdev->bars[nr].quirks, quirk, next);
> >
> > + /*
> > + * Allow user to override dsm size using x-igd-gms option, in multiples
> > of
> > + * 32MiB. This option should only be used when the desired size cannot be
> > + * set from DVMT Pre-Allocated option in host BIOS.
> > + */
> > + if (vdev->igd_gms) {
> > + if (gen < 8 && vdev->igd_gms <= 0x10) {
>
> This doesn't work as intended for values larger than 0x10. For those values,
> qemu ignores the generation and set GMS as it would be a gen 8 or later device.
>
> > + gmch &= ~(IGD_GMCH_GEN6_GMS_MASK << IGD_GMCH_GEN6_GMS_SHIFT);
> > + gmch |= vdev->igd_gms << IGD_GMCH_GEN6_GMS_SHIFT;
> > + } else if (vdev->igd_gms <= 0x40) {
> > + gmch &= ~(IGD_GMCH_GEN8_GMS_MASK << IGD_GMCH_GEN8_GMS_SHIFT);
> > + gmch |= vdev->igd_gms << IGD_GMCH_GEN8_GMS_SHIFT;
> > + } else {
> > + error_report("Unsupported IGD GMS value 0x%x", vdev->igd_gms);
We clearly know the upper limit of valid values for the device
generation, can we include that in the error report? Thanks,
Alex
> > + }
> > + }
> > +
> > ggms_size = igd_gtt_memory_size(gen, gmch);
> > gms_size = igd_stolen_memory_size(gen, gmch);
> >
>
next prev parent reply other threads:[~2024-12-04 22:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 13:35 [PATCH v2 0/9] vfio/igd: Enable legacy mode on more devices Tomita Moeko
2024-12-03 13:35 ` [PATCH v2 1/9] vfio/igd: remove unsupported device ids Tomita Moeko
2024-12-03 13:35 ` [PATCH v2 2/9] vfio/igd: align generation with i915 kernel driver Tomita Moeko
2024-12-03 16:07 ` Corvin Köhne
2024-12-04 22:36 ` Alex Williamson
2024-12-05 9:26 ` Tomita Moeko
2024-12-03 13:35 ` [PATCH v2 3/9] vfio/igd: canonicalize memory size calculations Tomita Moeko
2024-12-03 16:12 ` Corvin Köhne
2024-12-04 22:35 ` Alex Williamson
2024-12-05 10:13 ` Tomita Moeko
2024-12-03 13:35 ` [PATCH v2 4/9] vfio/igd: add Gemini Lake and Comet Lake device ids Tomita Moeko
2024-12-03 16:15 ` Corvin Köhne
2024-12-03 13:35 ` [PATCH v2 5/9] vfio/igd: add Alder/Raptor/Rocket/Ice/Jasper " Tomita Moeko
2024-12-03 16:18 ` Corvin Köhne
2024-12-03 13:35 ` [PATCH v2 6/9] vfio/igd: add macro for declaring mirrored registers Tomita Moeko
2024-12-03 16:22 ` Corvin Köhne
2024-12-04 22:35 ` Alex Williamson
2024-12-03 13:35 ` [PATCH v2 7/9] vfio/igd: emulate GGC register in mmio bar0 Tomita Moeko
2024-12-04 22:35 ` Alex Williamson
2024-12-03 13:35 ` [PATCH v2 8/9] vfio/igd: emulate BDSM in mmio bar0 for gen 6-10 devices Tomita Moeko
2024-12-03 16:24 ` Corvin Köhne
2024-12-03 13:35 ` [PATCH v2 9/9] vfio/igd: add x-igd-gms option back to set DSM region size for guest Tomita Moeko
2024-12-03 16:30 ` Corvin Köhne
2024-12-04 22:35 ` Alex Williamson [this message]
2024-12-03 20:12 ` [PATCH v2 0/9] vfio/igd: Enable legacy mode on more devices Alex Williamson
2024-12-04 15:08 ` Tomita Moeko
2024-12-29 16:43 ` Tomita Moeko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241204153528.5059341e.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=C.Koehne@beckhoff.com \
--cc=clg@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tomitamoeko@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).