From: "Derrick, Jonathan" <jonathan.derrick@intel.com>
To: "lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"hch@infradead.org" <hch@infradead.org>
Cc: "Kalakota, SushmaX" <sushmax.kalakota@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Patel, Nirmal" <nirmal.patel@intel.com>,
"helgaas@kernel.org" <helgaas@kernel.org>
Subject: Re: [PATCH 0/5] Legacy direct-assign mode
Date: Mon, 22 Mar 2021 22:55:46 +0000 [thread overview]
Message-ID: <804d2bff5bbe8e80004cbcbeaed3245b1acedf28.camel@intel.com> (raw)
In-Reply-To: <20210322194811.GA2141770@infradead.org>
On Mon, 2021-03-22 at 19:48 +0000, Christoph Hellwig wrote:
> On Mon, Mar 22, 2021 at 12:28:37PM +0000, Lorenzo Pieralisi wrote:
> > > 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 seems like a bad idea. What are these other hypervisors? AFAIK
> there are no purely userspace hypervisors, so in other words what you
> propose here is only for unsupported external modules.
Any of the type 1 hypervisors here:
https://en.wikipedia.org/wiki/Hypervisor
>
> I don't think we shoud merge something like this.
prev parent reply other threads:[~2021-03-22 22:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 22:51 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
2021-03-22 19:48 ` Christoph Hellwig
2021-03-22 22:55 ` 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=804d2bff5bbe8e80004cbcbeaed3245b1acedf28.camel@intel.com \
--to=jonathan.derrick@intel.com \
--cc=hch@infradead.org \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=nirmal.patel@intel.com \
--cc=sushmax.kalakota@intel.com \
--subject='Re: [PATCH 0/5] Legacy direct-assign mode' \
/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
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).