From: Niklas Schnelle <schnelle@linux.ibm.com>
To: Ramesh Errabolu <ramesh@linux.ibm.com>, linux-pci@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
driver-core@lists.linux.dev,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Lukas Wunner" <lukas@wunner.de>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Leon Romanovsky" <leon@kernel.org>,
"Peter Oberparleiter" <oberpar@linux.ibm.com>,
"Matthew Rosato" <mjrosato@linux.ibm.com>,
"Gerd Bayer" <gbayer@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Farhan Ali" <alifm@linux.ibm.com>
Subject: Re: [PATCH v5 1/1] PCI: hotplug: Add 'uevent' sysfs attribute to trigger slot events
Date: Tue, 07 Jul 2026 11:15:28 +0200 [thread overview]
Message-ID: <66fdb5ef25cdf733729b74b703de1a43b6b6a0af.camel@linux.ibm.com> (raw)
In-Reply-To: <20260706200244.91130-2-ramesh@linux.ibm.com>
On Mon, 2026-07-06 at 15:02 -0500, Ramesh Errabolu wrote:
> Add a write-only 'uevent' sysfs attribute for synthesizing
> uevents for a PCI slot. This extends the existing uevent
> support which emits a KOBJ_ADD uevent in pci_hp_add() with
> the ability to replay such uevents for cold plugged devices.
> As such events are only emitted by hotplug capable PCI slots
> so is the support for synthesizing them.
>
> The change was validated by manually triggering 'add' uevent
> for a specific hotplug PCI slot:
>
> $ echo "add $(uuidgen)" | sudo tee \
> /sys/bus/pci/slots/<slot-id>/uevent
>
> Signed-off-by: Ramesh Errabolu <ramesh@linux.ibm.com>
> Reviewed-by: Niklas Schnelle <schnelle@linux.ibm.com>
> Tested-by: Niklas Schnelle <schnelle@linux.ibm.com>
> ---
> drivers/pci/hotplug/pci_hotplug_core.c | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/drivers/pci/hotplug/pci_hotplug_core.c b/drivers/pci/hotplug/pci_hotplug_core.c
> index fadcf98a8a66..c3634b1cc7a8 100644
> --- a/drivers/pci/hotplug/pci_hotplug_core.c
> +++ b/drivers/pci/hotplug/pci_hotplug_core.c
> @@ -173,12 +173,27 @@ static ssize_t presence_read_file(struct pci_slot *pci_slot, char *buf)
>
> static struct pci_slot_attribute hotplug_slot_attr_presence = {
> .attr = {.name = "adapter", .mode = S_IFREG | S_IRUGO},
> .show = presence_read_file,
> };
>
> +static ssize_t uevent_write_file(struct pci_slot *slot,
> + const char *buf, size_t len)
> +{
> + int rc;
> +
> + rc = kobject_synth_uevent(&slot->kobj, buf, len);
> + return rc ? rc : len;
> +}
> +
> +static struct pci_slot_attribute hotplug_slot_attr_uevent = {
> + .attr = {.name = "uevent", .mode = S_IFREG | 0200},
> + .show = NULL,
As Bjorn Helgaas noted on v4 this ".show = NULL" is unnecessary. This
feedback should have been incorporated. And without that change there
is, as far as I can tell, no change vs v4 so this should have been
"[PATCH RESEND]" which Bjorn also told you in the same mail.
Thanks,
Niklas
[0] https://lore.kernel.org/linux-pci/20260521144853.GA163149@bhelgaas/
prev parent reply other threads:[~2026-07-07 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 20:02 [PATCH v5 0/1] PCI: hotplug: Add support for synthesizing slot uevents Ramesh Errabolu
2026-07-06 20:02 ` [PATCH v5 1/1] PCI: hotplug: Add 'uevent' sysfs attribute to trigger slot events Ramesh Errabolu
2026-07-07 9:15 ` Niklas Schnelle [this message]
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=66fdb5ef25cdf733729b74b703de1a43b6b6a0af.camel@linux.ibm.com \
--to=schnelle@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=alifm@linux.ibm.com \
--cc=bhelgaas@google.com \
--cc=driver-core@lists.linux.dev \
--cc=gbayer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kw@linux.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mjrosato@linux.ibm.com \
--cc=oberpar@linux.ibm.com \
--cc=ramesh@linux.ibm.com \
/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