linux-kernel - [PATCH 0/2] Add dev_sysdata and use it for ACPI

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-next>] [day] [month] [year] [list]

Date:	Thu, 09 Nov 2006 11:45:21 +1100
From:	Benjamin Herrenschmidt <benh@....ibm.com>
To:	Linux Kernel list <linux-kernel@...r.kernel.org>
Cc:	Len Brown <len.brown@...el.com>, Andrew Morton <akpm@...l.org>,
	Greg KH <greg@...ah.com>
Subject: [PATCH 0/2] Add dev_sysdata and use it for ACPI

As discussed on linux PCI, these 2 patches:

 - Add a dev_sysdata structure to struct device whose content is arch
specific. It will allow architectures like powerpc, arm, i386, ... who
need different types of DMA ops for busses and other kind of auxilliary
data for devices in general (numa node id, firmware data, etc...) to put
them in there, without bloating all architectures. The patch adds an
empty definition for the structure to all architectures.

 - As an example (patch test built but not test booted), I removed ACPI
usage of device->firmware_data, removed the firmware_data field
completely from struct device (as it was, apparently, the only user),
and instead used an "acpi_handle" field in x86 and x86_64 dev_sysdata.

I'd like to adapt my pending 2.6.20 patch set to use that instead of my
current "device_ext" thingy I've been doing, but that would mean having
an ack from Greg to merge the first patch in 2.6.20. Thus I'd like
feedback asap. The second patch is less critial, though Len is free to
take it and do whatever he wants with it :-)

Cheers,
Ben.



-
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/