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  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]
Date:	Thu, 15 Mar 2012 11:01:12 -0700
From:	Yinghai Lu <>
To:	Bjorn Helgaas <>
Cc:	Jesse Barnes <>, x86 <>,
	Andrew Morton <>,
	Linus Torvalds <>,
	Greg Kroah-Hartman <>,,,
	Len Brown <>,
Subject: Re: [PATCH v2 24/37] PCI, ACPI: Add pci_root_hp hot removal
 notification support.

On Thu, Mar 15, 2012 at 10:53 AM, Bjorn Helgaas <> wrote:
> Sure, the 'echo "\_SB.PCIB 3" > /proc/acpi/sci/notify' way looks more
> like physical hotadd/remove because it is basically injecting the
> notify event that the hardware/BIOS should be generating itself.  But
> it is platform-specific and therefore unacceptable as a general user
> interface.
> Using /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/remove would be a
> more generic way.  The PNP0A08:00/remove implementation would
> basically turn into an acpi_pci_root_remove() call, just like the
> 'echo "\_SB.PCIB 3" > /proc/acpi/sci/notify' does.

if the users can not find _SB.PCIB etc, they may not find

so /sys/class/pci_bus/0000:80/remove is more easy for them?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists