From: Hannes Reinecke <hare@suse.de>
To: Jordan Hargrave <Jordan_Hargrave@dell.com>, bhelgaas@google.com
Cc: alexander.duyck@gmail.com, linux-pci@vger.kernel.org,
babu.moger@oracle.com, linux-kernel@vger.kernel.org,
jharg93@gmail.com
Subject: Re: [PATCH] Create sysfs entries for PCI VPDI and VPDR tags
Date: Fri, 19 Feb 2016 11:00:49 +0100 [thread overview]
Message-ID: <56C6E7D1.4@suse.de> (raw)
In-Reply-To: <1455825895-10951-1-git-send-email-Jordan_Hargrave@dell.com>
On 02/18/2016 09:04 PM, Jordan Hargrave wrote:
> The VPD-R is a readonly area of the PCI Vital Product Data region.
> There are some standard keywords for serial number, manufacturer,
> and vendor-specific values. Dell Servers use a vendor-specific
> tag to store number of ports and port mapping of partitioned NICs.
>
> info = VPD-Info string
> PN = Part Number
> SN = Serial Number
> MN = Manufacturer ID
> Vx = Vendor-specific (x=0..9 A..Z)
>
> This creates a sysfs subdirectory in the pci device: vpdattr with
> 'info', 'EC', 'SN', 'V0', etc. files containing the tag values.
>
> Signed-off-by: Jordan Hargrave <Jordan_Hargrave@dell.com>
Hmm. Can we first get an agreement on the PCI VPD parsing patches
I've posted earlier?
VPD parsing is really tricky, and we should aim on making the
read_vpd function robust enough before we begin putting things into
sysfs.
Also, I'm not utterly keen on this patchset.
The sysfs space is blown up with tiny pieces of information, which
can easily gotten via lspci, too.
Also, to my knowledge it's perfectly valid to _write_ to the VPD, in
which case the entire sysfs attribute setup would be invalided.
How do you propose to handle that?
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2016-02-19 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 20:04 [PATCH] Create sysfs entries for PCI VPDI and VPDR tags Jordan Hargrave
2016-02-19 10:00 ` Hannes Reinecke [this message]
2016-02-19 14:07 ` Jordan Hargrave
2016-02-19 14:18 ` Hannes Reinecke
2016-02-19 19:44 ` Jordan_Hargrave
2016-04-10 21:26 ` Bjorn Helgaas
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=56C6E7D1.4@suse.de \
--to=hare@suse.de \
--cc=Jordan_Hargrave@dell.com \
--cc=alexander.duyck@gmail.com \
--cc=babu.moger@oracle.com \
--cc=bhelgaas@google.com \
--cc=jharg93@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).