linux-kernel - Re: [PATCH 3/5] ACPI: Bind implicit GPE dependencies to PCI devices

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]

Message-Id: <201010060137.29369.rjw@sisk.pl>
Date:	Wed, 6 Oct 2010 01:37:29 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Matthew Garrett <mjg@...hat.com>
Cc:	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org
Subject: Re: [PATCH 3/5] ACPI: Bind implicit GPE dependencies to PCI devices

On Monday, October 04, 2010, Matthew Garrett wrote:
> Several platforms provide GPE information about devices in ACPI, but provide
> no ACPI methods to handle these at runtime. Provide a default handler for
> this case and bind it to PCI devices as they're discovered in ACPI space.
> Keep the methods associated in case they have side effects.

I think I'd prefer it if ACPICA maintained a list of devices to Notify() if
the given GPE triggers.  That would require us to redefine
acpi_gpe_can_wake() a bit, but that should be generally more
efficient.

Thanks,
Rafael
--
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/