linux-kernel - Re: [PATCH 3/3] pci: Add Virtual Channel to save/restore support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAErSpo653fTtNkMk9gNkXsCVgFuVPnJmhFw5rO6ytefbDSSEyA@mail.gmail.com>
Date:	Tue, 17 Dec 2013 14:57:39 -0700
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Alex Williamson <alex.williamson@...hat.com>
Cc:	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Don Dutile <ddutile@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/3] pci: Add Virtual Channel to save/restore support

On Tue, Dec 17, 2013 at 1:28 PM, Alex Williamson
<alex.williamson@...hat.com> wrote:
> On Tue, 2013-12-17 at 11:03 -0700, Bjorn Helgaas wrote:
>> On Tue, Dec 10, 2013 at 11:48:45AM -0700, Alex Williamson wrote:
>> >...
>> > +   pci_read_config_dword(dev->bus->self, pos2 + PCI_VC_PORT_REG1, &reg1);
>> > +   evcc = reg1 & PCI_VC_REG1_EVCC;
>>
>> I think PCI_VC_PORT_REG1 and PCI_VC_PORT_REG2 are mis-named and should be
>> changed to CAP1 and CAP2 or similar.  Almost everything here is a
>> "register."
>
> That's true, but it matches the name in the spec: "Port VC Capability
> Register 1/2".  Thanks,

Sure, but we use PCI_EXP_DEVCAP for the "Device Capabilities
Register," PCI_EXP_DEVCTL for the "Device Control Register," etc.  All
I'm saying is that "REG" doesn't convey as much information as "CAP."

Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/