From: Alex Williamson <alex.williamson@redhat.com>
To: qemu-devel@nongnu.org
Cc: clg@redhat.com
Subject: Re: [PATCH] hw/vfio/pci-quirks: Support alternate offset for GPUDirect Cliques
Date: Thu, 8 Jun 2023 11:46:30 -0600 [thread overview]
Message-ID: <20230608114630.0adc58ae.alex.williamson@redhat.com> (raw)
In-Reply-To: <20230608174211.3227138-1-alex.williamson@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
On Thu, 8 Jun 2023 11:42:11 -0600
Alex Williamson <alex.williamson@redhat.com> wrote:
> NVIDIA Turing and newer GPUs implement the MSI-X capability at the offset
> previously reserved for use by hypervisors to implement the GPUDirect
> Cliques capability. A revised specification provides an alternate
> location. Add a config space walk to the quirk to check for conflicts,
> allowing us to fall back to the new location or generate an error at the
> quirk setup rather than when the real conflicting capability is added
> should there be no available location.
>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
>
> The specification doesn't have a public home, but I've been given
> permission to post it to the list. Therefore I'll reply to this with
> the document attached and update the link in a v2 posting once that's
> available in the list archive.
Updated spec attached. Thanks,
Alex
[-- Attachment #2: NVIDIA GPUDirect with PCI Pass-Through Virtualization.pdf --]
[-- Type: application/pdf, Size: 168745 bytes --]
next prev parent reply other threads:[~2023-06-08 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 17:42 [PATCH] hw/vfio/pci-quirks: Support alternate offset for GPUDirect Cliques Alex Williamson
2023-06-08 17:46 ` Alex Williamson [this message]
2023-06-08 18:05 ` [PATCH v2] " Alex Williamson
2023-06-12 14:07 ` Cédric Le Goater
2023-06-12 15:05 ` Alex Williamson
2023-06-14 12:37 ` Cédric Le Goater
2023-06-14 15:01 ` Alex Williamson
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=20230608114630.0adc58ae.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).