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 17:28:26 +0100 [thread overview]
Message-ID: <20111108162826.GD5182@amd.com> (raw)
In-Reply-To: <20111103034359.10286.19062.stgit@bling.home>
On Wed, Nov 02, 2011 at 11:53:56PM -0400, Alex Williamson wrote:
> More consistency cleanups. Drop the _OFF, separate and indent
> CTRL/CAP/STATUS bit definitions, fix that PASID_CAP doesn't
> actually report the ENABLE bit.
>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
>
> Joerg, I can't test this, so you may want to make sure I'm not
> breaking your API. The March 31, 2011 version of the PASID ECN
> shows bit 0 of the PASID capability register as reserved, not
> an indicator of support for or status of the enable bit.
> Presumably the entire capability wouldn't be included if it
> can't be enabled. With the below, pci_enable_pasid() now checks
> the right bit, but also pci_pasid_features() no longer masks in
> bit 0, but being reserved, it should have been clear anyway.
Looks like you are only renaming stuff. I don't see the real point but I
also don't object unless this will be merged upstream soon. I plan to
push the code using these capabilities for the next merge-window and if
this one will me merged then too it will cause a lot of pain.
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 16:44 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 [this message]
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
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=20111108162826.GD5182@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