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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20060730111747.6554f7de.kamezawa.hiroyu@jp.fujitsu.com>
Date:	Sun, 30 Jul 2006 11:17:47 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	Andi Kleen <ak@...e.de>
Cc:	discuss@...-64.org, kmannth@...ibm.com,
	linux-kernel@...r.kernel.org, lhms-devel@...ts.sourceforge.net,
	akpm@...l.org, haveblue@...ibm.com, darnok@...ibm.com
Subject: Re: [discuss] [Patch] 2/5 in support of hot-add memory x86_64
 create arch_find_node

On Sat, 29 Jul 2006 18:25:15 +0200
Andi Kleen <ak@...e.de> wrote:

> 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
> 
Hi,  Keith 

I don't like insert such a check (nid < 0) in add_memory(), either.
Could you add it before calling add_memory() ?
(for example, find_pxm parh in acpi's add memory code.)

-Kame

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