From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [RFC PATCH 1/8]: PVH: Basic and preparatory changes Date: Fri, 17 Aug 2012 15:36:04 -0400 Message-ID: <20120817193604.GA4573@phenom.dumpdata.com> References: <20120815175724.3405043a@mantra.us.oracle.com> <20120816114650.4db2079f@mantra.us.oracle.com> <20120817122014.3c3387b5@mantra.us.oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20120817122014.3c3387b5@mantra.us.oracle.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: Mukesh Rathor Cc: "Xen-devel@lists.xensource.com" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org > > For example in balloon.c we are probably only interested in memory > > related behavior, so checking for XENFEAT_auto_translated_physmap > > should be enough. In other parts of the code we might want to check > > for xen_pv_domain(). If xen_pv_domain() and > > XENFEAT_auto_translated_physmap are not enough, we could introduce > > another small XENFEAT that specifies that the domain is running in a > > HVM container. This way they are all reusable. > > yeah, I thought about that, but wasn't sure what the implications would > be for a guest thats not PVH but has auto xlated physmap, if there's > such a possibility. If you guys think thats not an issue, I can change > it. dom0_shadow=on on the hypervisor mode enables that in PV mode.