qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Corvin Köhne" <corvin.koehne@gmail.com>
To: "Alex Williamson" <alex.williamson@redhat.com>,
	"Cédric Le Goater" <clg@redhat.com>
Cc: qemu-devel@nongnu.org, Tony Krowiak <akrowiak@linux.ibm.com>,
	Eric Farman	 <farman@linux.ibm.com>,
	Eric Auger <eric.auger@redhat.com>,
	 tomitamoeko@gmail.com
Subject: Re: [PATCH v2] vfio: Add property documentation
Date: Fri, 14 Feb 2025 10:31:08 +0100	[thread overview]
Message-ID: <ef8108aa73c693cc54c08c81a14201138b14172f.camel@gmail.com> (raw)
In-Reply-To: <20250213144513.32b3241f.alex.williamson@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1787 bytes --]

On Thu, 2025-02-13 at 14:45 -0700, Alex Williamson wrote:
> On Thu, 13 Feb 2025 14:50:50 +0100
> Cédric Le Goater <clg@redhat.com> wrote:
> > +    /*
> > +     * IGD
> > +     */
> > +
> > +    object_class_property_set_description(klass, /* 2.7 */
> > +                                          "x-igd-opregion",
> > +                                          "Add IGD OpRegion support for
> > (headless system)");
> 
> [Cc Tomita and Corvin have more recent understanding of IGD options]
> 
> Not necessarily for headless systems, unless others have better
> suggestions, maybe just "Expose host IGD OpRegion table to guest".
> 

Sounds good. Note that it's required for the Intel GOP (EFI driver) and the
Windows driver. So, it's mandatory for non headless systems.

> > +    object_class_property_set_description(klass, /* 2.7 (See c4c45e943e51)
> > */
> > +                                          "x-igd-gms",
> > +                                          "Add Intel graphics legacy mode
> > device assignment support. "
> > +                                          "Assign 00:02.0 from the host to
> > 00:02.0 in the VM");
> 
> Not really.  Tomita added a useful comment and commit log in
> 37f05a59e869.  Perhaps:
> 
> "Override DVMT Pre-Allocated value for IGD stolen memory. (32MiB units)"

Nit: This sets the Graphics Mode Select value of the GMCH Graphics Control
register. While we currently only support values in the range of 0x00 - 0x40, I
don't see a reason to not support 0xF0 - 0xFE which uses 4 MiB increments.


-- 
Kind regards,
Corvin

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-02-14  9:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13 13:50 [PATCH v2] vfio: Add property documentation Cédric Le Goater
2025-02-13 14:17 ` BALATON Zoltan
2025-02-13 14:48   ` Cédric Le Goater
2025-02-13 14:45 ` Eric Auger
2025-02-13 14:49   ` Cédric Le Goater
2025-02-13 21:45 ` Alex Williamson
2025-02-14  9:31   ` Corvin Köhne [this message]
2025-02-14 11:03     ` Tomita Moeko
2025-02-14 13:05   ` Cédric Le Goater
2025-03-05 11:16     ` Joao Martins
2025-03-05 13:13       ` Cédric Le Goater
2025-03-11 16:44         ` Joao Martins
2025-03-11 17:43           ` Cédric Le Goater
2025-03-11 17:49             ` Joao Martins
2025-02-14 13:54   ` Cédric Le Goater

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=ef8108aa73c693cc54c08c81a14201138b14172f.camel@gmail.com \
    --to=corvin.koehne@gmail.com \
    --cc=akrowiak@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=clg@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=farman@linux.ibm.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).