Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762352Ab0GUFDf (ORCPT ); Wed, 21 Jul 2010 01:03:35 -0400 Received: from sh.osrg.net ([192.16.179.4]:38240 "EHLO sh.osrg.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933495Ab0GUFDA (ORCPT ); Wed, 21 Jul 2010 01:03:00 -0400 Date: Wed, 21 Jul 2010 13:58:16 +0900 To: akataria@vmware.com Cc: konrad.wilk@oracle.com, fujita.tomonori@lab.ntt.co.jp, ak@linux.intel.com, lenb@kernel.org, x86@kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, petr@vmware.com Subject: Re: swiotlb detection should be memory hotplug aware ? From: FUJITA Tomonori In-Reply-To: <1279664097.21596.43.camel@ank32.eng.vmware.com> References: <20100316124556.GA25340@phenom.dumpdata.com> <1268866113.20507.26.camel@ank32> <1279664097.21596.43.camel@ank32.eng.vmware.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20100721135750Z.fujita.tomonori@lab.ntt.co.jp> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (sh.osrg.net [192.16.179.4]); Wed, 21 Jul 2010 13:58:18 +0900 (JST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 789 Lines: 14 On Tue, 20 Jul 2010 15:14:57 -0700 Alok Kataria wrote: > Reviving a 4 month old thread. > I am still waiting for any clues on this question below. Basically, you want to add hot-plug memory and enable swiotlb, right? We can't start swiotlb reliably after a system starts. See dma32_reserve_boatmen() and dma32_free_bootmem(). What we do is reserving huge memory in DMA32 zone for swiotlb and releasing it if we find that we don't need swiotlb. We can't find enough memory for swiotlb in dma32 after a system starts. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/