From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755308Ab0FHNrM (ORCPT ); Tue, 8 Jun 2010 09:47:12 -0400 Received: from rcsinet10.oracle.com ([148.87.113.121]:65256 "EHLO rcsinet10.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755138Ab0FHNrK (ORCPT >); Tue, 8 Jun 2010 09:47:10 -0400 Date: Tue, 8 Jun 2010 09:46:37 -0400 From: Konrad Rzeszutek Wilk To: Stefano Stabellini Cc: "linux-kernel@vger.kernel.org" , "jeremy@goop.org" , "xen-devel@lists.xensource.com" , "Yaozu (Eddie) Dong" , "ddutile@redhat.com" , "sheng@linux.intel.com" Subject: Re: [Xen-devel] [PATCH 02/12] early PV on HVM Message-ID: <20100608134637.GA5998@phenom.dumpdata.com> References: <1275570645-27189-1-git-send-email-stefano.stabellini@eu.citrix.com> <1275570645-27189-2-git-send-email-stefano.stabellini@eu.citrix.com> <20100604202008.GB17645@phenom.dumpdata.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) X-Auth-Type: Internal IP X-Source-IP: acsinet15.oracle.com [141.146.126.227] X-CT-RefId: str=0001.0A090202.4C0E49CD.0043:SCFMA922111,ss=1,fgs=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > > + HYPERVISOR_shared_info = (struct shared_info *)shared_info_page; > > > + > > > + /* Don't do the full vcpu_info placement stuff until we have a > > > + possible map and a non-dummy shared_info. */ > > > > Might want to mention where the full vpcu placement is done. > > The comment is not accurate, we actually don't do any vcpu_info > placement on hvm because it is not very useful there. > Better just to remove the comment (I have done so in my tree). > > > > + per_cpu(xen_vcpu, 0) = &HYPERVISOR_shared_info->vcpu_info[0]; > > So.. what is the purpose of the per_cpu(xen_vcpu, 0) then?