From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mukesh Rathor Subject: Re: [PATCH 17/18 V2]: PVH xen: PVH dom0 creation... Date: Tue, 26 Mar 2013 16:42:11 -0700 Message-ID: <20130326164211.7295fce6@mantra.us.oracle.com> References: <20130315180645.59f8618e@mantra.us.oracle.com> <51483D9602000078000C6A56@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51483D9602000078000C6A56@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Konrad Rzeszutek Wilk , xen-devel List-Id: xen-devel@lists.xenproject.org On Tue, 19 Mar 2013 09:27:34 +0000 "Jan Beulich" wrote: > >>> On 16.03.13 at 02:06, Mukesh Rathor > >>> wrote: > > Finally, the hardest. Mostly modify construct_dom0() to boot PV > > dom0 in PVH mode. Introduce, opt_dom0pvh, which when specified in > > the command line, causes dom0 to boot in PVH mode. > > Now that Konrad mentioned that PVH is intended for 64-bit guests > only, I fail to see where this restriction is being enforced in this > patch. And it would certainly have been worthwhile to state that Yup. I forgot to mention that in the cover letter, and forgot to add a check for that. Will be in the next patch for sure. Right now, there is no code in linux for 32bit PVH btw. > more prominently, even more so since Konrad keeps telling people > that this patch set is expected to initiate a deprecation phase for > the PV MMU interfaces in Linux (which then would mean no 32-bit > PV guest support at all anymore). Well, we definitely intend to head that way. And it is most feasible to do this big work in steps. We are by no means done when this phase I patch is checked in. I've already outlined phase II, III etc.. Having some baseline working in xen will allow me to progress faster, and allow to add others to contribute. I think I should leave PVH disabled until we have reached a satisfactory point, and we can enable it in future. thanks Mukesh