From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
"Raj, Ashok" <ashok.raj@intel.com>,
Jean-Philippe Brucker <jean-philippe.brucker@arm.com>,
"Lu, Baolu" <baolu.lu@intel.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>, "Wu, Hao" <hao.wu@intel.com>
Subject: Re: IOASID set token
Date: Tue, 7 Jul 2020 08:38:08 -0700 [thread overview]
Message-ID: <20200707083808.27adc859@jacob-builder> (raw)
In-Reply-To: <20200707100718.GA151594@myrica>
Hi Jean,
All other points agreed.
On Tue, 7 Jul 2020 12:07:18 +0200
Jean-Philippe Brucker <jean-philippe@linaro.org> wrote:
> > > For the moment, though, we could actually specialize the IOASID
> > > API to only take an mm_struct as token.
> > That would be fine with VT-d. We can use init_mm for host PASID set,
> > process mm for VM set.
>
> I'm not fond of using init_mm for the host PASID set. Does it need a
> token at all?
No need to use init_mm at all, probably can do without a token as well.
Just need to allocate a set for the native usage. I will give it a try.
Thanks,
Jacob
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2020-07-07 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 6:29 IOASID set token Jacob Pan
2020-07-02 13:48 ` Jacob Pan
2020-07-06 10:30 ` Jean-Philippe Brucker
2020-07-06 20:51 ` Jacob Pan
2020-07-07 10:07 ` Jean-Philippe Brucker
2020-07-07 15:38 ` Jacob Pan [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=20200707083808.27adc859@jacob-builder \
--to=jacob.jun.pan@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@intel.com \
--cc=hao.wu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe.brucker@arm.com \
--cc=jean-philippe@linaro.org \
--cc=kevin.tian@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).