From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754155AbaAFKwp (ORCPT ); Mon, 6 Jan 2014 05:52:45 -0500 Received: from smtp02.citrix.com ([66.165.176.63]:56587 "EHLO SMTP02.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752082AbaAFKwm (ORCPT ); Mon, 6 Jan 2014 05:52:42 -0500 X-IronPort-AV: E=Sophos;i="4.95,612,1384300800"; d="scan'208";a="87836532" Message-ID: <52CA8AF7.9040305@citrix.com> Date: Mon, 6 Jan 2014 10:52:39 +0000 From: David Vrabel User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20121215 Iceowl/1.0b1 Icedove/3.0.11 MIME-Version: 1.0 To: Konrad Rzeszutek Wilk CC: , , , , , Mukesh Rathor Subject: Re: [PATCH v13 11/19] xen/pvh: Secondary VCPU bringup (non-bootup CPUs) References: <1388777916-1328-1-git-send-email-konrad.wilk@oracle.com> <1388777916-1328-12-git-send-email-konrad.wilk@oracle.com> In-Reply-To: <1388777916-1328-12-git-send-email-konrad.wilk@oracle.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.2.76] X-DLP: MIA2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/01/14 19:38, Konrad Rzeszutek Wilk wrote: > From: Mukesh Rathor > > The VCPU bringup protocol follows the PV with certain twists. > From xen/include/public/arch-x86/xen.h: > > Also note that when calling DOMCTL_setvcpucontext and VCPU_initialise > for HVM and PVH guests, not all information in this structure is updated: > > - For HVM guests, the structures read include: fpu_ctxt (if > VGCT_I387_VALID is set), flags, user_regs, debugreg[*] > > - PVH guests are the same as HVM guests, but additionally use ctrlreg[3] to > set cr3. All other fields not used should be set to 0. > > This is what we do. We piggyback on the 'xen_setup_gdt' - but modify > a bit - we need to call 'load_percpu_segment' so that 'switch_to_new_gdt' > can load per-cpu data-structures. It has no effect on the VCPU0. > > We also piggyback on the %rdi register to pass in the CPU number - so > that when we bootup a new CPU, the cpu_bringup_and_idle will have > passed as the first parameter the CPU number (via %rdi for 64-bit). [...] > --- a/arch/x86/xen/enlighten.c > +++ b/arch/x86/xen/enlighten.c > @@ -1409,14 +1409,19 @@ static void __init xen_boot_params_init_edd(void) > * Set up the GDT and segment registers for -fstack-protector. Until > * we do this, we have to be careful not to call any stack-protected > * function, which is most of the kernel. > + * > + * Note, that it is refok - because the only caller of this after init "Note, this is __ref because..." David