[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 7 Jul 2021 20:58:22 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: "Raj, Ashok" <ashok.raj@...el.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
"Dey, Megha" <megha.dey@...el.com>, linux-kernel@...r.kernel.org,
"Jiang, Dave" <dave.jiang@...el.com>,
"Tian, Kevin" <kevin.tian@...el.com>,
"Pan, Jacob jun" <jacob.jun.pan@...el.com>,
"Liu, Yi L" <yi.l.liu@...el.com>,
"Kumar, Sanjay K" <sanjay.k.kumar@...el.com>,
"Van De Ven, Arjan" <arjan.van.de.ven@...el.com>,
"Williams, Dan J" <dan.j.williams@...el.com>,
"Shankar, Ravi V" <ravi.v.shankar@...el.com>
Subject: Re: Programming PASID in IMS entries
On Wed, Jul 07, 2021 at 03:12:16PM -0700, Raj, Ashok wrote:
> Hi Thomas
>
> On Wed, Jul 07, 2021 at 10:50:52AM +0200, Thomas Gleixner wrote:
> > Megha,
> >
> > On Wed, Jul 07 2021 at 09:49, Megha Dey wrote:
> > > Per your suggestions during the last meeting, we wanted to confirm the
> > > sequence to program the PASID into the IMS entries:
> > >
> > > 1. Add a PASID member to struct msi_desc (Add as part of a union. Other
> > > source-id's such as Jason's vm-id can be added to it)
> >
> > Yes. Though we also discussed storing the default PASID in struct device
> > to begin with which is then copied to the msi_desc entries during
> > allocation.
>
> Using default PASID in struct device will work for sub-devices until the
> guest needs to enable ENQCMD support. Since the guest kernel can ask for an
> interrupt by specifying something in the descriptor submitted via ENQCMD.
> Using the PASID in struct device won't be sufficient.
Could you could store a pasid table in the struct device and index it
by vector?
Jason
Powered by blists - more mailing lists