public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 3/4] PCI: Add implementation for PRI capability
Date: Sun, 30 Oct 2011 15:57:07 +0100	[thread overview]
Message-ID: <20111030145706.GH32555@amd.com> (raw)
In-Reply-To: <CAMuHMdUJU+4n73P6Kc920+ZeJZouCc52QVa1Emanjiiu1kmq-w@mail.gmail.com>

On Sat, Oct 29, 2011 at 03:36:13PM -0400, Geert Uytterhoeven wrote:
> On Tue, Sep 27, 2011 at 15:57, Joerg Roedel <joerg.roedel@amd.com> wrote:
> > Implement the necessary functions to handle PRI capabilities
> > on PCIe devices. With PRI devices behind an IOMMU can signal
> > page fault conditions to software and recover from such
> > faults.
> >
> > Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
> > ---
> >  drivers/pci/Kconfig      |    9 +++
> >  drivers/pci/ats.c        |  167 ++++++++++++++++++++++++++++++++++++++++++++++
> >  include/linux/pci-ats.h  |   42 ++++++++++++
> >  include/linux/pci_regs.h |   12 +++
> >  4 files changed, 230 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/pci/Kconfig b/drivers/pci/Kconfig
> > index 1d8ce83..fb1e9707 100644
> > --- a/drivers/pci/Kconfig
> > +++ b/drivers/pci/Kconfig
> > @@ -85,6 +85,15 @@ config PCI_IOV
> >
> >          If unsure, say N.
> >
> > +config PCI_PRI
> > +       bool "PCI PRI support"
> 
> Shouldn't this depend on PCI?
> 
> It doesn't seem to hurt on PCI-less platforms, but I prefer not seeing
> PCI-related questions when CONFIG_PCI is not set.

You are right, I send a fix soon. Thanks for the report.

	Joerg

-- 
AMD Operating System Research Center

Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632


  reply	other threads:[~2011-10-30 14:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27 13:57 [PATCH 0/4 v2] PCI: Add support for PASID capability Joerg Roedel
2011-09-27 13:57 ` [PATCH 1/4] PCI: Move ATS implementation into own file Joerg Roedel
2011-10-14 16:06   ` Jesse Barnes
2011-09-27 13:57 ` [PATCH 2/4] PCI: Export ATS functions to modules Joerg Roedel
2011-09-27 13:57 ` [PATCH 3/4] PCI: Add implementation for PRI capability Joerg Roedel
2011-10-29 19:36   ` Geert Uytterhoeven
2011-10-30 14:57     ` Roedel, Joerg [this message]
2011-09-27 13:57 ` [PATCH 4/4] PCI: Add support for PASID capability Joerg Roedel
2011-10-07 12:31 ` [PATCH 0/4 v2] " Joerg Roedel
2011-10-07 14:05   ` Jesse Barnes
2011-10-07 14:59     ` Bjorn Helgaas
  -- strict thread matches above, loose matches on Subject: below --
2011-09-22 15:49 [PATCH 0/4] Support for PRI and " Joerg Roedel
2011-09-22 15:49 ` [PATCH 3/4] PCI: Add implementation for PRI capability 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=20111030145706.GH32555@amd.com \
    --to=joerg.roedel@amd.com \
    --cc=bhelgaas@google.com \
    --cc=geert@linux-m68k.org \
    --cc=jbarnes@virtuousgeek.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox