From: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
Bob Liu <liubo95@huawei.com>, valmiki <valmikibow@gmail.com>,
Alex Williamson <alex.williamson@redhat.com>
Cc: "Lan, Tianyu" <tianyu.lan@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"Pan, Jacob jun" <jacob.jun.pan@intel.com>
Subject: Re: Support SVM without PASID
Date: Fri, 11 Aug 2017 10:25:20 +0100 [thread overview]
Message-ID: <017d8f2f-d72d-c037-1769-339da392e24f@arm.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D190D6EDB7@SHSMSX101.ccr.corp.intel.com>
On 11/08/17 07:41, Tian, Kevin wrote:
[...]
>>> Hi Jean,
>>>
>>> I think there is another way to support SVM without PASID.
>>>
>>> Suppose there is a device in the same SOC-chip, the device access memory
>> through SMMU(using internal bus instead of PCIe)
>>> Once page fault, the device send an event with (vaddr, substreamID) to
>> SMMU, then SMMU triggers an event interrupt.
>>>
>>> In the event interrupt handler, we can implement the same logic as PRI
>> interrupt in your patch.
>>> What do you think about that?
>> What you're describing is the SMMU stall model for platform devices. From
>> the driver perspective it's the same as PRI and PASID (SubstreamID=PASID).
>>
>> When a stall-capable device accesses unmapped memory, the SMMU parks
>> the
>> transaction and sends an event marked "stall" on the event queue, with a
>> stall tag (STAG, roughly equivalent to PRG Index). The OS handles the
>> fault and sends a CMD_RESUME command with the status and the STAG.
>> Then
>> the SMMU completes the access or terminates it.
>
> Can such platform device send multiple SubstreamIDs, or one ID per
> device?
Yes, SVM-capable platform devices should issue multiple SubstreamIDs and a
single StreamID (equivalent to VT-d's Source-ID).
Thanks,
Jean
next prev parent reply other threads:[~2017-08-11 9:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 17:03 Support SVM without PASID valmiki
2017-07-08 20:02 ` Alex Williamson
2017-07-09 3:15 ` valmiki
2017-07-09 9:29 ` Liu, Yi L
2017-07-10 0:14 ` Bob Liu
2017-07-10 19:31 ` Jerome Glisse
2017-07-12 16:23 ` valmiki
2017-07-11 10:56 ` Jean-Philippe Brucker
2017-07-12 16:27 ` valmiki
2017-07-12 16:48 ` Jean-Philippe Brucker
2017-07-22 2:05 ` valmiki
2017-08-01 8:26 ` Jean-Philippe Brucker
2017-08-01 17:38 ` valmiki
2017-08-01 18:40 ` Jean-Philippe Brucker
2017-08-05 5:14 ` valmiki
2017-08-07 10:31 ` Jean-Philippe Brucker
2017-08-07 12:18 ` Bob Liu
2017-08-07 12:52 ` Jean-Philippe Brucker
2017-08-08 0:51 ` Bob Liu
2017-08-09 15:01 ` Jean-Philippe Brucker
2017-08-11 6:41 ` Tian, Kevin
2017-08-11 9:25 ` Jean-Philippe Brucker [this message]
2017-08-11 9:36 ` Bob Liu
2017-08-12 12:10 ` valmiki
2017-08-14 7:49 ` Tian, Kevin
2017-08-28 13:10 ` Bharat Kumar Gogada
2017-08-29 1:32 ` Tian, Kevin
2017-08-04 1:49 ` Tian, Kevin
2017-08-04 9:42 ` Jean-Philippe Brucker
2017-08-11 6:29 ` Tian, Kevin
2017-08-11 16:25 ` Raj, Ashok
2017-08-14 8:00 ` Tian, Kevin
2017-08-14 9:07 ` Jean-Philippe Brucker
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=017d8f2f-d72d-c037-1769-339da392e24f@arm.com \
--to=jean-philippe.brucker@arm.com \
--cc=alex.williamson@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liubo95@huawei.com \
--cc=tianyu.lan@intel.com \
--cc=valmikibow@gmail.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).