From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mukesh Rathor Subject: Re: XENFEAT_supervisor_mode_kernel ??? Date: Thu, 20 Nov 2008 15:03:21 -0800 Message-ID: <4925ECB9.4010706@oracle.com> References: Reply-To: mukesh.rathor@oracle.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 Oh, cool. I was looking at syscalls on PV x86_64 guests, and one of my thoughts was running in HVM mode but do all MMU stuff using hypercalls like PV. Other than having to change the hyp domain create portions, setting things up, is there a technical reason it can't be done today... thanks, Mukesh Keir Fraser wrote: > On 20/11/08 22:42, "Mukesh Rathor" wrote: > >> I'm trying ot figure out what that's all about? I see in 64 PV domU, it's >> being checked prior to returning from syscall. On the xen side, I see it tied >> to supervisor_mode_kernel, but the only info I find is changelog comment which >> suggests it's purpose is to allow dom0 run in ring 0... So why the check in a >> domU kernel? > > It's useful if the hypervisor runs the guest kernel in ring 0. Current Xen > doesn't do that, but in future we may run 64-bit PV guests in HVM context as > that may actually be faster. > > -- Keir >