From: Joerg Roedel <joro@8bytes.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] PCI: Add support for PASID capability
Date: Tue, 27 Sep 2011 00:15:39 +0200 [thread overview]
Message-ID: <20110926221539.GG15002@8bytes.org> (raw)
In-Reply-To: <CAErSpo7Vb7avbsP3eG=3huCewW4QBL7oMoXr2TjMCaWEvFgB0Q@mail.gmail.com>
On Mon, Sep 26, 2011 at 02:58:58PM -0600, Bjorn Helgaas wrote:
> On Thu, Sep 22, 2011 at 9:49 AM, Joerg Roedel <joerg.roedel@amd.com> wrote:
> > Devices supporting the PASID capability can use multiple
> > contexts on an IOMMU at the same time. This patch adds
> > support to manage that capability.
>
> These all look reasonable to me.
>
> Is there anything else useful you could say in the PASID Kconfig help
> text? I'm guessing it stands for "PCI Address Space ID" or something,
> but I have no idea why I might want to enable it.
PASID stands for Process Address Space ID, it basically allows a PCI
device to access multiple IO address spaces at the same time using an
IOMMU. Users should enable it when they want to compile an IOMMU driver
into the kernel that supports PASIDs for the translated devices.
I'll add all that information to the Kconfig help. Thanks a lot for your
feedback :)
> I didn't coordinate very well with Jesse. I'm hoping he'll be back
> before the 3.2 merge window, but I think we have a few patches queued
> up now, and it might be useful to have them in linux-next for a while
> before he returns. I'll look into that.
Great, thanks again.
Regards,
Joerg
next prev parent reply other threads:[~2011-09-26 22:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 15:49 [PATCH 0/4] Support for PRI and PASID capability Joerg Roedel
2011-09-22 15:49 ` [PATCH 1/4] PCI: Move ATS implementation into own file Joerg Roedel
2011-09-22 15:49 ` [PATCH 2/4] PCI: Export ATS functions to modules Joerg Roedel
2011-09-22 15:49 ` [PATCH 3/4] PCI: Add implementation for PRI capability Joerg Roedel
2011-09-22 15:49 ` [PATCH 4/4] PCI: Add support for PASID capability Joerg Roedel
2011-09-26 20:58 ` Bjorn Helgaas
2011-09-26 22:15 ` Joerg Roedel [this message]
2011-09-28 19:18 ` Valdis.Kletnieks
2011-09-29 9:26 ` Roedel, Joerg
2011-09-26 14:26 ` [PATCH 0/4] Support for PRI and " Joerg Roedel
2011-09-26 20:42 ` Bjorn Helgaas
2011-09-26 20:59 ` Joerg Roedel
-- strict thread matches above, loose matches on Subject: below --
2011-09-27 13:57 [PATCH 0/4 v2] PCI: Add support for " Joerg Roedel
2011-09-27 13:57 ` [PATCH 4/4] " Joerg Roedel
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=20110926221539.GG15002@8bytes.org \
--to=joro@8bytes.org \
--cc=bhelgaas@google.com \
--cc=jbarnes@virtuousgeek.org \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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.