public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ramesh Errabolu <ramesh@linux.ibm.com>
To: Niklas Schnelle <schnelle@linux.ibm.com>, linux-pci@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	Bjorn Helgaas <bhelgaas@google.com>,
	Lukas Wunner <lukas@wunner.de>,
	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>
Subject: Re: [PATCH v2 1/1] PCI/hotplug: Add 'uevent' sysfs attribute to trigger slot events
Date: Mon, 20 Apr 2026 14:37:46 -0500	[thread overview]
Message-ID: <5c1498cb-5de6-41be-8db7-f76a385237c0@linux.ibm.com> (raw)
In-Reply-To: <91f26c77330be0783aad379dd1b04bb4c1411713.camel@linux.ibm.com>

Thanks for testing and also giving me the review-by

Regards,
Ramesh


On 4/17/2026 4:53 AM, Niklas Schnelle wrote:
> On Thu, 2026-04-16 at 16:39 -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>
>> ---
>>   drivers/pci/hotplug/pci_hotplug_core.c | 25 +++++++++++++++++++++++++
>>   1 file changed, 25 insertions(+)
>>
> Sorry for the review delay. This looks good to me and will really help
> with udev rule execution for devices which are discovered in standby
> state during boot and thus currently don't create any uevents. Of
> course to work by default this still requires a systemd/udev addition
> that I know you're also working on.
>
> Consequently, I tested the uevent synthesization with both slots with a
> configured (slot powered on) and standby (slot powered off) PCI
> function.
>
> Feel free to add:
>
> Reviewed-by: Niklas Schnelle <schnelle@linux.ibm.com>
> Tested-by: Niklas Schnelle <schnelle@linux.ibm.com>
>
> Thanks,
> Niklas

  reply	other threads:[~2026-04-20 19:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-16 21:39 [PATCH v2 0/1] PCI/hotplug: Add 'uevent' sysfs attribute to trigger slot events Ramesh Errabolu
2026-04-16 21:39 ` [PATCH v2 1/1] " Ramesh Errabolu
2026-04-17  9:53   ` Niklas Schnelle
2026-04-20 19:37     ` Ramesh Errabolu [this message]
2026-04-21 17:13   ` Krzysztof Wilczyński
2026-04-21 21:38     ` Ramesh Errabolu
2026-04-22  4:44       ` Krzysztof Wilczyński
     [not found]         ` <742b8820-4bfe-40ef-85a9-5704af038ee1@linux.ibm.com>
2026-04-22 17:13           ` 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=5c1498cb-5de6-41be-8db7-f76a385237c0@linux.ibm.com \
    --to=ramesh@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=bhelgaas@google.com \
    --cc=gbayer@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --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=schnelle@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