linux-kernel - Re: RFC [PATCH] x86: try to remove arch_get_ram

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: <20080618084850.40adb1a8.akpm@linux-foundation.org>
Date:	Wed, 18 Jun 2008 08:48:50 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	"Keshavamurthy, Anil S" <anil.s.keshavamurthy@...el.com>,
	Jan Engelhardt <jengelh@....de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: RFC [PATCH] x86: try to remove arch_get_ram_range

On Wed, 18 Jun 2008 16:07:26 +0200 Ingo Molnar <mingo@...e.hu> wrote:

> 
> * Yinghai Lu <yhlu.kernel@...il.com> wrote:
> 
> > want to remove arch_get_ram_range, and use early_node_map instead.
> 
> (small request: please include diffstat output in your patches in the 
> future if possible: "quilt refresh --diffstat" will do that - this way 
> people will know why they were Cc:-ed)
> 
> this touches the MM:
> 
>  arch/x86/mm/init_32.c     |    6 +++--
>  drivers/pci/intel-iommu.c |   51 +++++++++++++++++++++++++++++++++-------------
>  include/linux/mm.h        |    2 -
>  mm/page_alloc.c           |   10 ++++++---
>  4 files changed, 49 insertions(+), 20 deletions(-)
> 
> but has many dependencies on ongoing arch/x86 work. Andrew, is this 
> change fine with with you?
> 

Beats me - I don't even have a mm/page_alloc.c:work_with_active_regions()
in my tree.
--
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/