linux-kernel - Re: [discuss] [Patch] 2/5 in support of hot-add memory x86_64 create arch_find

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200607291825.16308.ak@suse.de>
Date:	Sat, 29 Jul 2006 18:25:15 +0200
From:	Andi Kleen <ak@...e.de>
To:	discuss@...-64.org, kmannth@...ibm.com
Cc:	lkml <linux-kernel@...r.kernel.org>,
	lhms-devel <lhms-devel@...ts.sourceforge.net>,
	andrew <akpm@...l.org>, dave hansen <haveblue@...ibm.com>,
	kame <kamezawa.hiroyu@...fujitsu.com>, konrad <darnok@...ibm.com>
Subject: Re: [discuss] [Patch] 2/5 in support of hot-add memory x86_64 create arch_find_node

On Saturday 29 July 2006 04:52, keith mannthey wrote:
>   With the advent of the new ACPI hot-plug memory driver and mechanism
> is needed to deal with ACPI add memory events that do not contain the
> pxm (node) information. I do not believe that the add-event is required
> to contain this information so I create a arch_find_node generic layer
> used in the generic add_memory function.
>
>   If add_memory is called with node < 0 arch_find_node is invoked to
> fine the correct node to add the memory. This created the generic
> construct of arch_find_node.

It would be cleaner to always call add_memory from architecture specific
code instead of such ugly hooks

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