From: Ingo Molnar Subject: Re: [PATCH 00 of 14] swiotlb/x86: lay groundwork for xen dom0 use of swiotlb Date: Fri, 19 Dec 2008 09:18:35 +0100 Message-ID: <20081219081835.GA9097@elte.hu> References: <4949296F.7000701@goop.org> <20081218015705Z.fujita.tomonori@lab.ntt.co.jp> <20081219114808C.fujita.tomonori@lab.ntt.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20081219114808C.fujita.tomonori@lab.ntt.co.jp> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: FUJITA Tomonori Cc: jeremy@goop.org, xen-devel@lists.xensource.com, ian.campbell@citrix.com, beckyb@kernel.crashing.org, joerg.roedel@amd.com, x86@kernel.org, linux-kernel@vger.kernel.org, benh@kernel.crashing.org List-Id: xen-devel@lists.xenproject.org * FUJITA Tomonori wrote: > On Thu, 18 Dec 2008 12:17:54 -0600 > Becky Bruce wrote: > > > > Can you be more specific? What architecture is plan to use highmem > > > support in swiotlb? > > > > 32-bit powerpc needs this support - I was actually about to push a > > similar set of patches. We have several processors that support 36 > > bits of physical address space and do not have any iommu capability. > > The rest of the kernel support for those processors is now in place, > > so swiotlb is the last piece of the puzzle for that to be fully > > functional. I need to take a closer look at this series to see > > exactly what it's doing and how it differs from what I've been testing. > > Ah, thanks, > > Then I accept that highmem support in lib/swiotbl.c is generically > useful and we have to live with the ugly complication due to it. Great! And we of course want to make the best possible job here - so whenever you notice any area that could be done better and less intrusively, please mention it. Ingo