From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Levin Subject: Re: [PATCH 21/28] kvm tools: Add --hugetlbfs option to specify memory path Date: Wed, 07 Dec 2011 08:01:11 +0200 Message-ID: <1323237671.8489.7.camel@lappy> References: <4EDD8F06.7080805@ozlabs.org> <1323160375.3882.13.camel@lappy> <4EDEB4E2.7080304@ozlabs.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org To: Matt Evans Return-path: In-Reply-To: <4EDEB4E2.7080304@ozlabs.org> Sender: kvm-ppc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Wed, 2011-12-07 at 11:35 +1100, Matt Evans wrote: > On 06/12/11 19:32, Sasha Levin wrote: > > I'm seeing hugetlbfs_path being passed around, but I don't see anything > > that actually does something with it. > > > > Did it get into a different patch? or maybe it wasn't 'git add'ed? > > It's actually moved in preparation for the later "[PATCH 1/8] kvm tools: Add > initial SPAPR PPC64 architecture support" patch, which uses it. I could've > mushed that into the later PPC series but I thought it'd be clearer to do the > generic/x86 stuff separately. I actually would like to see everything moved into the generic code out of the PPC series :) hugetlb allocation should probably be done in the generic code as it would work on x86 as well. -- Sasha.