From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sheng Yang Subject: Re: [PATCH][v2] Hybrid extension support in Xen Date: Tue, 2 Feb 2010 22:08:37 +0800 Message-ID: <201002022208.37234.sheng@linux.intel.com> References: Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Tuesday 02 February 2010 22:03:31 Keir Fraser wrote: > On 02/02/2010 13:37, "Sheng Yang" wrote: > >>> 1. Enable SMP support through VCPU_OP in arch_set_info_guest(). > >> > >> What does that mean and why would we want it? > > > > It's not a good description, sorry... We need a entry address and boot up > > code AP. For that purpose, I reuse VCPUOP_initialise and VCPUOP_up > > hypercall. The former guest set the entry address of AP, the later one > > boot up them. For this, I add some code in arch_set_info_guest() to > > initialize the AP(mostly what we did after INIT-SIPI-SIPI sequence), > > that's what I means here... > > Okay, so that leads to the obvious next question: why do you want to avoid > using INIT-SIPI-SIPI? > Because we don't have IOAPIC/LAPIC... -- regards Yang, Sheng