public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: "Roedel, Joerg" <Joerg.Roedel@amd.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"jbarnes@virtuousgeek.org" <jbarnes@virtuousgeek.org>,
	"bhelgaas@google.com" <bhelgaas@google.com>
Subject: Re: [PATCH] pci: More PRI/PASID cleanup
Date: Tue, 08 Nov 2011 11:20:06 -0700	[thread overview]
Message-ID: <1320776406.19116.42.camel@bling.home> (raw)
In-Reply-To: <20111108175410.GH5182@amd.com>

On Tue, 2011-11-08 at 18:54 +0100, Roedel, Joerg wrote:
> On Tue, Nov 08, 2011 at 10:31:58AM -0700, Alex Williamson wrote:
> > On Tue, 2011-11-08 at 18:17 +0100, Roedel, Joerg wrote:
> > > On Tue, Nov 08, 2011 at 09:44:30AM -0700, Alex Williamson wrote:
> > > 
> > > > bit 0 (PCI_PASID_ENABLE) is reserved in the CAP register...
> > > 
> > > Is it? Which spec are you using? In my version it is not reserved but
> > > states if it is supported to set the enable-bit.
> > 
> > Latest I can find is the March 31, 2011 PASID ECN, which just lists that
> > bit as reserved.
> 
> Okay, my one is older and there it is stated as I implemented it. I will
> check with reality first before changing the code...

My guess is that someone asked why a device would ever expose this table
if it didn't support enable as a capability.  So, I wouldn't be
surprised if your hardware sets it, but it's probably just as safe to
assume enable is supported if the PASID table exists.  Thanks,

Alex

> > I can drop it if need be, was just trying to do some cleanup on the
> > consistency of pci_reg.h before adding a bunch more defines to help
> > bounds checking and parsing for vfio-pci.  Unless my spec is outdated,
> > it seems like there's more than an aesthetic change here though, so
> > resolving the conflicts with your latest work might be warranted.
> 
> Fine with me. The best is probably when I carry this change forward
> (when Jesse is ok with that) and put my changes on-top of that.
> 
> Thanks,
> 
> 	Joerg
> 




  reply	other threads:[~2011-11-08 18:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03  3:53 [PATCH] pci: More PRI/PASID cleanup Alex Williamson
2011-11-08 16:28 ` Roedel, Joerg
2011-11-08 16:44   ` Alex Williamson
2011-11-08 17:17     ` Roedel, Joerg
2011-11-08 17:31       ` Alex Williamson
2011-11-08 17:54         ` Roedel, Joerg
2011-11-08 18:20           ` Alex Williamson [this message]
2011-11-09  9:59             ` Roedel, Joerg

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=1320776406.19116.42.camel@bling.home \
    --to=alex.williamson@redhat.com \
    --cc=Joerg.Roedel@amd.com \
    --cc=bhelgaas@google.com \
    --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