Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756087Ab1DOOTa (ORCPT ); Fri, 15 Apr 2011 10:19:30 -0400 Received: from smtp02.lnh.mail.rcn.net ([207.172.157.102]:39449 "EHLO smtp02.lnh.mail.rcn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753964Ab1DOOT3 (ORCPT ); Fri, 15 Apr 2011 10:19:29 -0400 X-Greylist: delayed 572 seconds by postgrey-1.27 at vger.kernel.org; Fri, 15 Apr 2011 10:19:29 EDT Date: Fri, 15 Apr 2011 10:08:46 -0400 From: Konrad Rzeszutek Wilk To: Rusty Russell Cc: Stratos Psomadakis , linux-kernel@vger.kernel.org Subject: Re: Two questions about paravirt boot sequence(head_32.S) Message-ID: <20110415140846.GA32334@dumpdata.com> References: <4DA6CD8F.6080206@ece.ntua.gr> <8762qhavaa.fsf@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8762qhavaa.fsf@rustcorp.com.au> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 710 Lines: 15 On Thu, Apr 14, 2011 at 09:40:05PM +0930, Rusty Russell wrote: > On Thu, 14 Apr 2011 13:33:51 +0300, Stratos Psomadakis wrote: > > 2)I think that xen doesn't use any more the hardware subarch boot > > parameter, and uses a 'different' path/boot sequence, hence the > > xen_entry in head_32.S is not needed any more. Am I missing something? > > Yep, Xen never actually used it. Does lguest use it? It looked like a neat idea - what happened? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/