From: "Raj, Ashok" <ashok.raj@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
"Dey, Megha" <megha.dey@intel.com>,
linux-kernel@vger.kernel.org, "Jiang,
Dave" <dave.jiang@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"Pan, Jacob jun" <jacob.jun.pan@intel.com>,
"Liu, Yi L" <yi.l.liu@intel.com>,
"Kumar, Sanjay K" <sanjay.k.kumar@intel.com>,
"Van De Ven, Arjan" <arjan.van.de.ven@intel.com>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"Shankar, Ravi V" <ravi.v.shankar@intel.com>,
Ashok Raj <ashok.raj@intel.com>
Subject: Re: Programming PASID in IMS entries
Date: Thu, 8 Jul 2021 14:33:44 -0700 [thread overview]
Message-ID: <20210708213344.GA347913@otc-nc-03> (raw)
In-Reply-To: <87v95kod9f.ffs@nanos.tec.linutronix.de>
Hi Thomas,
On Thu, Jul 08, 2021 at 08:45:48PM +0200, Thomas Gleixner wrote:
> Ashok,
>
> >> > IMS core owns the format of the entries right now vs device specific driver.
> >> > I suppose your use case requiring a vm_id might have a different format.
> >> > So this is yet another one the core needs to learn and adapt?
> >>
> >> All entry format stuff is device specific, it shouldn't be in "core"
> >> code.
> >
> > Well, this is how it started way back last year.
> >
> > https://lore.kernel.org/lkml/158751209583.36773.15917761221672315662.stgit@djiang5-desk3.ch.intel.com/
>
> Which is wrong on so many levels as we all know.
Sorry, I was just trying to point to Jason, that its how things started.
Since he was suggesting to have them as device specific.
>
> > Where the driver functions for mask/unmask/write_msg etc. So the core
> > needs
>
> Needs what?
Fat fingered that reply.. I completed it partially but moved to a different
sentence formation :-(
>
> > So the format or layout is device specific, but core can dictate the exact
> > message that needs to be written.
>
> Sorry, I don't grok what you want to say here.
Sorry it was unclear.. I meant things like compose_msg()
Cheers,
Ashok
next prev parent reply other threads:[~2021-07-08 21:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bd509e3d-f59d-1200-44ce-93cf9132bd8c@intel.com>
2021-07-07 8:50 ` Thomas Gleixner
2021-07-07 12:15 ` Jason Gunthorpe
2021-07-07 23:41 ` Tian, Kevin
2021-07-07 22:12 ` Raj, Ashok
2021-07-07 23:58 ` Jason Gunthorpe
2021-07-08 0:33 ` Raj, Ashok
2021-07-08 12:08 ` Jason Gunthorpe
2021-07-08 14:36 ` Raj, Ashok
2021-07-08 18:45 ` Thomas Gleixner
2021-07-08 21:33 ` Raj, Ashok [this message]
2021-07-08 13:00 ` Thomas Gleixner
2021-07-07 23:51 ` Tian, Kevin
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=20210708213344.GA347913@otc-nc-03 \
--to=ashok.raj@intel.com \
--cc=arjan.van.de.ven@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=jacob.jun.pan@intel.com \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=megha.dey@intel.com \
--cc=ravi.v.shankar@intel.com \
--cc=sanjay.k.kumar@intel.com \
--cc=tglx@linutronix.de \
--cc=yi.l.liu@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
all inboxes | Powered by JetHome®