From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
To: Alex Williamson <alex.williamson@redhat.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, 8 Nov 2011 18:17:25 +0100 [thread overview]
Message-ID: <20111108171725.GE5182@amd.com> (raw)
In-Reply-To: <1320770670.19116.23.camel@bling.home>
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.
> Which means we need to check CTRL, not CAP to see if it was previously
> enabled... or maybe this check is entirely wrong and we're was trying to
> see if enable is supported.
I will check how this looks in my test environment.
> And nobody exposes PCI_PASID_ENABLE because it doesn't exist as a
> capability.
>
> It's easy to see this if the bit definitions are named appropriately and
> specified per register instead of being lumped together as "close
> enough". Thanks,
I don't object against your renames as long as it doesn't cause
merge-conflicts with what I plan to send upstream.
Thanks,
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
next prev parent reply other threads:[~2011-11-08 17:17 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 [this message]
2011-11-08 17:31 ` Alex Williamson
2011-11-08 17:54 ` Roedel, Joerg
2011-11-08 18:20 ` Alex Williamson
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=20111108171725.GE5182@amd.com \
--to=joerg.roedel@amd.com \
--cc=alex.williamson@redhat.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