From: "Krzysztof Wilczyński" <kw@linux.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/4] PCI/sysfs: Add pci_dev_resource_attr_is_visible() helper
Date: Fri, 10 Sep 2021 19:21:01 +0200 [thread overview]
Message-ID: <20210910172101.GA1314672@rocinante> (raw)
In-Reply-To: <YTtm4e9a/gS5Swga@kroah.com>
Hi Greg,
[...]
> > pci_dev_config_attr_is_visible(..., struct bin_attribute *a, ...)
> > {
> > a->size = PCI_CFG_SPACE_SIZE; # <-- set size in global attr
> > ...
> > }
> >
> > static struct bin_attribute *pci_dev_config_attrs[] = {
> > &bin_attr_config, NULL,
> > };
> > static const struct attribute_group pci_dev_config_attr_group = {
> > .bin_attrs = pci_dev_config_attrs,
> > .is_bin_visible = pci_dev_config_attr_is_visible,
> > };
> >
> > pci_device_add
> > device_add
> > device_add_attrs
> > device_add_groups
> > sysfs_create_groups
> > internal_create_groups
> > internal_create_group
> > create_files
> > grp->is_bin_visible()
> > sysfs_add_file_mode_ns
> > size = battr->size # <-- copy size from attr
> > __kernfs_create_file(..., size, ...)
> > kernfs_new_node
> > __kernfs_new_node
> >
>
> You can create a dynamic attribute and register that. I think some
> drivers/busses do that today to handle this type of thing.
Some static attributes users don't set size today or simply set it to 0, so
then we report 0 bytes in userspace for each such attribute via the backing
i-node.
Would you be open to the idea of adding a .size() callback so that static
attributes users could set size using more proper channels, or do you think
leaving it being set to 0 is fine?
Krzysztof
next prev parent reply other threads:[~2021-09-10 17:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 21:22 [PATCH 0/4] PCI: Convert dynamic PCI resources sysfs objects into static Krzysztof Wilczyński
2021-08-25 21:22 ` [PATCH 1/4] PCI/sysfs: Add pci_dev_resource_attr_is_visible() helper Krzysztof Wilczyński
2021-08-26 23:35 ` Bjorn Helgaas
2021-08-27 12:11 ` Greg Kroah-Hartman
2021-08-27 22:23 ` Bjorn Helgaas
2021-09-10 14:08 ` Greg Kroah-Hartman
2021-09-10 17:21 ` Krzysztof Wilczyński [this message]
2021-09-11 10:13 ` Greg Kroah-Hartman
2021-09-13 19:47 ` Bjorn Helgaas
2021-09-14 5:06 ` Greg Kroah-Hartman
2021-09-10 16:12 ` Krzysztof Wilczyński
2021-08-25 21:22 ` [PATCH 2/4] PCI/sysfs: Add pci_dev_resource_attr() macro Krzysztof Wilczyński
2021-08-26 21:12 ` Bjorn Helgaas
2021-08-25 21:22 ` [PATCH 3/4] PCI/sysfs: Add pci_dev_resource_group() macro Krzysztof Wilczyński
2021-08-25 21:22 ` [PATCH 4/4] PCI/sysfs: Convert PCI resource files to static attributes Krzysztof Wilczyński
2021-08-25 23:02 ` [PATCH 0/4] PCI: Convert dynamic PCI resources sysfs objects into static Krzysztof Wilczyński
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=20210910172101.GA1314672@rocinante \
--to=kw@linux.com \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@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