From: "Derrick, Jonathan" <jonathan.derrick@intel.com>
To: "lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Patel, Nirmal" <nirmal.patel@intel.com>,
"helgaas@kernel.org" <helgaas@kernel.org>,
"Kalakota, Sushma" <sushma.kalakota@intel.com>
Subject: Re: [PATCH 0/5] Legacy direct-assign mode
Date: Mon, 22 Mar 2021 15:25:34 +0000 [thread overview]
Message-ID: <36c52c3cefe532b1cfaeccd122ef5520cd5fa2cd.camel@intel.com> (raw)
In-Reply-To: <20210322122837.GC11469@e121166-lin.cambridge.arm.com>
On Mon, 2021-03-22 at 12:28 +0000, Lorenzo Pieralisi wrote:
> On Fri, Nov 20, 2020 at 03:51:39PM -0700, Jon Derrick wrote:
> > This set adds a legacy direct-assign mode. Newer enterprise hardware has
> > physical addressing hints to assist device passthrough to guests that needs to
> > correctly program bridge windows with physical addresses. Some customers are
> > using a legacy method that relies on the VMD subdevice domain's root port
> > windows to be written with the physical addresses. This method also allows
> > other hypervisors besides QEMU/KVM to perform guest passthrough.
> >
> > This patchset adds a host and guest mode to write the physical address
> > information to the root port registers in the host and read them in the guest,
> > and restore them in both cases on module unload.
> >
> > This patchset also folds in the VMD subdevice domain secondary bus reset
> > patchset [1] to clear the domain prior to guest passthrough.
> >
> > [1] https://patchwork.kernel.org/project/linux-pci/cover/20200928010557.5324-1-jonathan.derrick@intel.com/
> >
> > Jon Derrick (5):
> > PCI: vmd: Reset the VMD subdevice domain on probe
> > PCI: Add a reset quirk for VMD
> > PCI: vmd: Add offset translation helper
> > PCI: vmd: Pass features to vmd_get_phys_offsets()
> > PCI: vmd: Add legacy guest passthrough mode
> >
> > drivers/pci/controller/vmd.c | 200 ++++++++++++++++++++++++++++++++++++++-----
> > drivers/pci/quirks.c | 48 +++++++++++
> > 2 files changed, 227 insertions(+), 21 deletions(-)
>
> Hi Jon,
>
> it is unclear to me where we are with this series, please let me know.
>
> Thanks,
> Lorenzo
Hi Lorenzo,
We can drop this series for now. We may revive it in the future with
modifications to the reset sequence.
Best,
Jon
next prev parent reply other threads:[~2021-03-22 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 22:51 [PATCH 0/5] Legacy direct-assign mode Jon Derrick
2020-11-20 22:51 ` [PATCH 1/5] PCI: vmd: Reset the VMD subdevice domain on probe Jon Derrick
2020-11-20 22:51 ` [PATCH 2/5] PCI: Add a reset quirk for VMD Jon Derrick
2020-11-24 21:40 ` Bjorn Helgaas
2020-11-25 17:22 ` Derrick, Jonathan
2020-11-25 17:34 ` Alex Williamson
2020-11-20 22:51 ` [PATCH 3/5] PCI: vmd: Add offset translation helper Jon Derrick
2020-11-20 22:51 ` [PATCH 4/5] PCI: vmd: Pass features to vmd_get_phys_offsets() Jon Derrick
2020-11-20 22:51 ` [PATCH 5/5] PCI: vmd: Add legacy guest passthrough mode Jon Derrick
2021-03-22 12:28 ` [PATCH 0/5] Legacy direct-assign mode Lorenzo Pieralisi
2021-03-22 15:25 ` Derrick, Jonathan [this message]
2021-03-22 19:48 ` Christoph Hellwig
2021-03-22 22:55 ` Derrick, Jonathan
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=36c52c3cefe532b1cfaeccd122ef5520cd5fa2cd.camel@intel.com \
--to=jonathan.derrick@intel.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=nirmal.patel@intel.com \
--cc=sushma.kalakota@intel.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).