linux-kernel - Re: [PATCH] x86: Remove dma32_reserve

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]

Date:	Mon, 28 Mar 2011 18:22:13 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Yinghai Lu <yinghai@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: Remove dma32_reserve_bootmem


* Jesse Barnes <jbarnes@...tuousgeek.org> wrote:

> On Thu, 24 Mar 2011 09:03:26 +0100
> Ingo Molnar <mingo@...e.hu> wrote:
> 
> > 
> > * Yinghai Lu <yinghai@...nel.org> wrote:
> > 
> > > 
> > > That is workaround for holding dma32 buf when early bootmem could use up
> > > those range on system that have lots of RAM.
> > > 
> > > Now x86 is using memblock, and even nobootmem wrapper do top-down allocation.
> > > 
> > > So We could remove those not needed code now.
> > > 
> > > Signed-off-by: Yinghai Lu <yinghai@...nel.org>
> > > 
> > > ---
> > >  arch/x86/include/asm/pci.h |    2 -
> > >  arch/x86/kernel/pci-dma.c  |   64 ---------------------------------------------
> > >  arch/x86/kernel/setup.c    |    1
> > >  3 files changed, 67 deletions(-)
> > 
> > Cc:-ing Jesse - i suspect this should be handled by the PCI tree.
> 
> Please re-send, sounds good in theory but I'd like to see the patch.

It should be in your lkml folder, the first mail in this thread has the patch.

Thanks,

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