From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linux Driver Review <linux-drivers-review@eclists.intel.com>,
iommu@eclists.intel.com, Yi Liu <yi.l.liu@intel.com>,
Raj Ashok <ashok.raj@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
Lu Baolu <baolu.lu@linux.intel.com>, Wu Hao <hao.wu@intel.com>,
Yi Sun <yi.y.sun@intel.com>, Dave Jiang <dave.jiang@intel.com>,
linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>,
jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH v4 01/16] docs: Document IO Address Space ID (IOASID) APIs
Date: Fri, 19 Feb 2021 14:59:40 -0800 [thread overview]
Message-ID: <20210219145940.0ad35b08@jacob-builder> (raw)
In-Reply-To: <87im6op1bp.fsf@meer.lwn.net>
Hi Jon,
On Fri, 19 Feb 2021 07:41:14 -0700, Jonathan Corbet <corbet@lwn.net> wrote:
> Jacob Pan <jacob.jun.pan@linux.intel.com> writes:
>
> > IOASID is used to identify address spaces that can be targeted by device
> > DMA. It is a system-wide resource that is essential to its many users.
> > This document is an attempt to help developers from all vendors navigate
> > the APIs. At this time, ARM SMMU and Intel’s Scalable IO Virtualization
> > (SIOV) enabled platforms are the primary users of IOASID. Examples of
> > how SIOV components interact with the IOASID APIs are provided.
> >
> > Cc: Jonathan Corbet <corbet@lwn.net>
> > Cc: linux-doc@vger.kernel.org
> > Cc: Randy Dunlap <rdunlap@infradead.org>
> > Signed-off-by: Liu Yi L <yi.l.liu@intel.com>
> > Signed-off-by: Wu Hao <hao.wu@intel.com>
> > Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
> > ---
> > Documentation/driver-api/ioasid.rst | 696 ++++++++++++++++++++++++++++
> > 1 file changed, 696 insertions(+)
> > create mode 100644 Documentation/driver-api/ioasid.rst
>
> A detail, but an important one: you need to add this new file to
> index.rst so it gets built as part of the kernel docs.
>
will do for this and the cgroup one. thanks!
> Thanks,
>
> jon
Thanks,
Jacob
prev parent reply other threads:[~2021-02-19 22:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1613683288-89552-1-git-send-email-jacob.jun.pan@linux.intel.com>
2021-02-18 21:21 ` [PATCH v4 01/16] docs: Document IO Address Space ID (IOASID) APIs Jacob Pan
2021-02-19 7:28 ` [iommu] " Tian, Kevin
2021-02-19 14:41 ` Jonathan Corbet
2021-02-19 22:59 ` 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=20210219145940.0ad35b08@jacob-builder \
--to=jacob.jun.pan@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=corbet@lwn.net \
--cc=dave.jiang@intel.com \
--cc=hao.wu@intel.com \
--cc=iommu@eclists.intel.com \
--cc=kevin.tian@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-drivers-review@eclists.intel.com \
--cc=rdunlap@infradead.org \
--cc=yi.l.liu@intel.com \
--cc=yi.y.sun@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.