From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Stabellini Subject: Re: [PATCH 0 of 5] PV on HVM Xen Date: Wed, 17 Mar 2010 15:17:08 +0000 Message-ID: References: <201003171651.05220.sheng@linux.intel.com> <201003171718.37598.sheng@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Return-path: In-Reply-To: <201003171718.37598.sheng@linux.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Sheng Yang Cc: Jeremy Fitzhardinge , "xen-devel@lists.xensource.com" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On Wed, 17 Mar 2010, Sheng Yang wrote: > Seem not get enough update... > > OK, a new flag, adjustment in Xen. Right? > Yes, a new flag to signal the presence of a reliable clocksource on HVM; adjustments in Xen to make it work (keep in mind that my patch fix the problem only when tsc_mode==2 and we need to support tsc_mode==1 too). On the other hand we agreed that we don't need XEN_HVM_PV_EVTCHN_ENABLED and CONFIG_XEN_HVM_PV anymore. We probably don't need XEN_HVM_PV too for the moment, we might introduce it in the future when we actually add code that doesn't work on 32 bit. Finally I would still like the call to xen_guest_init to be moved afterwards: if we move it after kvm_guest_init we can be pretty sure that upstream is going to accept it. Besides ACPI is currently working with your patch series applied, when and if we break ACPI we'll worry about it. Jeremy, Ian, does this seem reasonable to you? The last point in particular? If you are sure that upstream will accept a hook in setup.c anyway I am ready to drop this.