From mboxrd@z Thu Jan 1 00:00:00 1970 From: Glauber Costa Subject: Re: [patch 02/18] x86: kvmclock: allocate pvclock shared memory area (v2) Date: Fri, 16 Nov 2012 11:06:49 +0400 Message-ID: <50A5E609.703@parallels.com> References: <20121115000823.285102321@redhat.com> <20121115000944.034452554@redhat.com> <50A520F3.8060105@parallels.com> <20121116020755.GB16948@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: , , , , , , To: Marcelo Tosatti Return-path: Received: from mx2.parallels.com ([64.131.90.16]:36823 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750730Ab2KPHHD (ORCPT ); Fri, 16 Nov 2012 02:07:03 -0500 In-Reply-To: <20121116020755.GB16948@amt.cnet> Sender: kvm-owner@vger.kernel.org List-ID: On 11/16/2012 06:07 AM, Marcelo Tosatti wrote: > > We want to expose the pvclock shared memory areas, which > the hypervisor periodically updates, to userspace. > > For a linear mapping from userspace, it is necessary that > entire page sized regions are used for array of pvclock > structures. > > There is no such guarantee with per cpu areas, therefore move > to memblock_alloc based allocation. > > Signed-off-by: Marcelo Tosatti > No further objections. Acked-by: Glauber Costa