From: Alex Williamson <alex.williamson@redhat.com>
To: valmiki <valmikibow@gmail.com>
Cc: iommu@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-pci@vger.kernel.org,
jean-Philippe Brucker <jean-philippe.brucker@arm.com>,
tianyu.lan@intel.com, kevin.tian@intel.com,
jacob.jun.pan@intel.com
Subject: Re: Support SVM without PASID
Date: Sat, 8 Jul 2017 14:02:57 -0600 [thread overview]
Message-ID: <20170708140257.2de02d63@w520.home> (raw)
In-Reply-To: <a30962a6-2240-9263-96cc-10da1b179fcc@gmail.com>
On Sat, 8 Jul 2017 22:33:01 +0530
valmiki <valmikibow@gmail.com> wrote:
> Hi,
>
> In SMMUv3 architecture document i see "PASIDs are optional,
> configurable, and of a size determined by the minimum
> of the endpoint".
>
> So if PASID's are optional and not supported by PCIe end point, how SVM
> can be achieved ?
It cannot be inferred from that statement that PASID support is not
required for SVM. AIUI, SVM is a software feature enabled by numerous
"optional" hardware features, including PASID. Features that are
optional per the hardware specification may be required for specific
software features. Thanks,
Alex
next prev parent reply other threads:[~2017-07-08 20:02 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 [this message]
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
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=20170708140257.2de02d63@w520.home \
--to=alex.williamson@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@intel.com \
--cc=jean-philippe.brucker@arm.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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).