From: "Derrick, Jonathan" <jonathan.derrick@intel.com>
To: "hch@infradead.org" <hch@infradead.org>
Cc: "lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"helgaas@kernel.org" <helgaas@kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Jakowski, Andrzej" <andrzej.jakowski@intel.com>
Subject: Re: [PATCH 0/1] KVM support for VMD devices
Date: Thu, 23 Apr 2020 15:18:10 +0000 [thread overview]
Message-ID: <f58982d0d37f86c8cf4d8769d42bea284e0c2825.camel@intel.com> (raw)
In-Reply-To: <20200423061631.GA12688@infradead.org>
On Wed, 2020-04-22 at 23:16 -0700, Christoph Hellwig wrote:
> On Wed, Apr 22, 2020 at 01:14:44PM -0400, Jon Derrick wrote:
> > The two patches (Linux & QEMU) add support for passthrough VMD devices
> > in QEMU/KVM. VMD device 28C0 already supports passthrough natively by
> > providing the Host Physical Address in a shadow register to the guest
> > for correct bridge programming.
> >
> > The QEMU patch emulates the 28C0 mode by creating a shadow register and
> > advertising its support by using QEMU's subsystem vendor/id.
> > The Linux patch matches the QEMU subsystem vendor/id to use the shadow
> > register.
>
> Please pick a different PCI ID for Qemu vs real hardware so that we
> can properly quirk them if they end up behaving differently due to
> hardware or software bugs.
Sure. Will look into that.
Thanks Christoph
Jon
prev parent reply other threads:[~2020-04-23 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 17:14 [PATCH 0/1] KVM support for VMD devices Jon Derrick
2020-04-23 6:16 ` Christoph Hellwig
2020-04-23 15:18 ` Derrick, Jonathan [this message]
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=f58982d0d37f86c8cf4d8769d42bea284e0c2825.camel@intel.com \
--to=jonathan.derrick@intel.com \
--cc=andrzej.jakowski@intel.com \
--cc=hch@infradead.org \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux-foundation.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).