Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Jacob Pan <jacob.pan@linux.microsoft.com>
Cc: Wei Liu <wei.liu@kernel.org>,
	Mukesh R <mrathor@linux.microsoft.com>,
	Alex Williamson <alex@shazbot.org>,
	hpa@zytor.com, robin.murphy@arm.com, robh@kernel.org,
	mhklinux@outlook.com, muislam@microsoft.com,
	namjain@linux.microsoft.com, magnuskulke@linux.microsoft.com,
	anbelski@linux.microsoft.com, linux-kernel@vger.kernel.org,
	linux-hyperv@vger.kernel.org, iommu@lists.linux.dev,
	linux-pci@vger.kernel.org, linux-arch@vger.kernel.org,
	kys@microsoft.com, haiyangz@microsoft.com, decui@microsoft.com,
	longli@microsoft.com, tglx@kernel.org, mingo@redhat.com,
	bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
	joro@8bytes.org, will@kernel.org, lpieralisi@kernel.org,
	kwilczynski@kernel.org, bhelgaas@google.com, arnd@arndb.de,
	"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>
Subject: Re: [PATCH v5 3/9] mshv: Introduce basic mshv bridge device for VFIO to build upon
Date: Thu, 3 Sep 2026 21:10:06 -0300	[thread overview]
Message-ID: <20260904001006.GO4157646@nvidia.com> (raw)
In-Reply-To: <20260903114647.00005a1f@linux.microsoft.com>

On Thu, Sep 03, 2026 at 11:46:47AM -0700, Jacob Pan wrote:
> Hi Jason,
> 
> On Thu, 3 Sep 2026 14:40:14 -0300
> Jason Gunthorpe <jgg@nvidia.com> wrote:
> 
> > On Thu, Sep 03, 2026 at 09:13:28AM -0700, Wei Liu wrote:
> > > > Does mshv use KVM at all? Can a kvm fd describe the partition?  
> > > 
> > > No. MSHV doesn't use KVM. We don't have a kvm fd. We have an mshv
> > > fd to describe the partition. They are different virtualization
> > > solutions.
> > > 
> > > In the ideal world, the fd should be hypervisor agnostic, not tied
> > > to kvm.  
> > 
> > There is a patch generalizing vfio to work on FDs instead of KVM
> > structures:
> > 
> >  https://patch.msgid.link/20260903-vfio-v2-1-ef4cd4190ae7@linux.ibm.com 
> > 
> > That's probably a good step long that line.
> Yeah, ideally, it would be removing/rename device/group->kvm to
> something like group/device->vm_file?

Maybe it could? Do you need the file in VFIO land or is what you
showed in the other message OK?

I think it should be broadly fine to pass in the file that way and
hold a reference on it in the viommu object..

Jason

  reply	other threads:[~2026-09-04  0:10 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31 22:34 [PATCH v5 0/9] PCI passthru on Hyper-V Mukesh R
2026-07-31 22:34 ` [PATCH v5 1/9] mshv: Provide a way to get partition ID if running in a VMM process Mukesh R
2026-07-31 22:47   ` sashiko-bot
2026-07-31 22:34 ` [PATCH v5 2/9] mshv: Add declarations and definitions for VFIO-MSHV bridge device Mukesh R
2026-07-31 22:42   ` sashiko-bot
2026-07-31 22:34 ` [PATCH v5 3/9] mshv: Introduce basic mshv bridge device for VFIO to build upon Mukesh R
2026-07-31 22:49   ` sashiko-bot
2026-09-02 18:19   ` Jacob Pan
2026-09-03 14:42     ` Jason Gunthorpe
2026-09-03 16:13       ` Wei Liu
2026-09-03 17:40         ` Jason Gunthorpe
2026-09-03 18:46           ` Jacob Pan
2026-09-04  0:10             ` Jason Gunthorpe [this message]
2026-09-03 18:34       ` Jacob Pan
2026-07-31 22:34 ` [PATCH v5 4/9] mshv: Add ioctl support for MSHV-VFIO bridge device Mukesh R
2026-07-31 22:49   ` sashiko-bot
2026-07-31 22:34 ` [PATCH v5 5/9] mshv: Import data structs around device passthru from hyperv headers Mukesh R
2026-07-31 22:45   ` sashiko-bot
2026-07-31 22:34 ` [PATCH v5 6/9] PCI: hv: Export hv_build_devid_type_pci() and change return type Mukesh R
2026-07-31 22:47   ` sashiko-bot
2026-08-18 22:14   ` Bjorn Helgaas
2026-07-31 22:34 ` [PATCH v5 7/9] x86/hyperv: Implement Hyper-V virtual IOMMU Mukesh R
2026-07-31 22:48   ` sashiko-bot
2026-08-05 12:48   ` Jason Gunthorpe
2026-08-18 21:01     ` Jacob Pan
2026-08-18 23:51       ` Jason Gunthorpe
2026-08-18 23:39     ` Mukesh R
2026-08-18 23:48       ` Jason Gunthorpe
2026-08-19  0:13         ` Mukesh R
2026-08-19 12:46           ` Jason Gunthorpe
2026-08-19 16:29             ` Jacob Pan
2026-08-19 16:33               ` Jason Gunthorpe
2026-07-31 22:34 ` [PATCH v5 8/9] mshv: Populate mmio mappings for PCI passthru Mukesh R
2026-07-31 22:54   ` sashiko-bot
2026-07-31 22:34 ` [PATCH v5 9/9] mshv: Disable movable regions upfront if device passthru Mukesh R
2026-07-31 22:57   ` sashiko-bot

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=20260904001006.GO4157646@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=alex@shazbot.org \
    --cc=anbelski@linux.microsoft.com \
    --cc=aneesh.kumar@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=decui@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=hpa@zytor.com \
    --cc=iommu@lists.linux.dev \
    --cc=jacob.pan@linux.microsoft.com \
    --cc=joro@8bytes.org \
    --cc=kwilczynski@kernel.org \
    --cc=kys@microsoft.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=longli@microsoft.com \
    --cc=lpieralisi@kernel.org \
    --cc=magnuskulke@linux.microsoft.com \
    --cc=mhklinux@outlook.com \
    --cc=mingo@redhat.com \
    --cc=mrathor@linux.microsoft.com \
    --cc=muislam@microsoft.com \
    --cc=namjain@linux.microsoft.com \
    --cc=robh@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=tglx@kernel.org \
    --cc=wei.liu@kernel.org \
    --cc=will@kernel.org \
    --cc=x86@kernel.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