From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754772Ab1C1QWY (ORCPT ); Mon, 28 Mar 2011 12:22:24 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:59382 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751750Ab1C1QWX (ORCPT ); Mon, 28 Mar 2011 12:22:23 -0400 Date: Mon, 28 Mar 2011 18:22:13 +0200 From: Ingo Molnar To: Jesse Barnes Cc: Yinghai Lu , Thomas Gleixner , "H. Peter Anvin" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] x86: Remove dma32_reserve_bootmem Message-ID: <20110328162213.GA20191@elte.hu> References: <4D8AD6E0.10307@kernel.org> <20110324080326.GA30812@elte.hu> <20110328091946.7ab9165f@jbarnes-desktop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110328091946.7ab9165f@jbarnes-desktop> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.3.1 -2.0 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Jesse Barnes wrote: > On Thu, 24 Mar 2011 09:03:26 +0100 > Ingo Molnar wrote: > > > > > * Yinghai Lu 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 > > > > > > --- > > > 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