linux-kernel - Re: [PATCH v2] Add option to passively listen for PCIE hotplug events

lists.openwall.net		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 linux-cve-announce 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:	Mon, 3 Nov 2008 14:43:14 +0100
From:	"Fabio Comolli" <fabio.comolli@...il.com>
To:	"Matthew Garrett" <mjg59@...f.ucam.org>
Cc:	"Grant Grundler" <grundler@...isc-linux.org>,
	linux-pci@...r.kernel.org, kristen.c.accardi@...el.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] Add option to passively listen for PCIE hotplug events

Hi.

On Mon, Nov 3, 2008 at 2:26 PM, Matthew Garrett <mjg59@...f.ucam.org> wrote:
> Various pieces of hardware (such as the Acer Aspire One and Asus EEE)
> use PCIE hotplug to change the state of devices in response to events
> such as the removal of SD cards or disabling the wireless radio.
> However, they do not provide firmware support for this. As a consequence
> pciehp will refuse to load and various things break.
>
> The existing workaround has been to use the pciehp_force option. This is
> undesirable as there is little guarantee that manipulating the power
> file in the slot directory will actually result in anything happening,
> leading to potential user confusion and hardware damage. This patch adds
> a new option, pciehp_passive. In this configuration pciehp will listen
> for events and notify the PCI core appropriately. However, it will not
> provide any user controllable sysfs attributes and so the risk of
> confusion or damage is averted. Any system slots that do have firmware
> support will continue to provide full functionality.
>
> Signed-off-by: Matthew Garrett <mjg@...hat.com>
>

On my system (a hp laptop) I have to use pciehp_force=1 to have the
service driver hpdriver loaded and an IRQ (MSI-Edge) assigned.

Does this patch mean that in the future I'd have to use the new
pciehp_passive=1 switch instead?

Sorry if I wasn't clear, I'm not an English native speaker.

Regards,
Fabio
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/