From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754620Ab3AXTYS (ORCPT ); Thu, 24 Jan 2013 14:24:18 -0500 Received: from mo-p00-ob.rzone.de ([81.169.146.160]:32079 "EHLO mo-p00-ob.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750975Ab3AXTYP (ORCPT ); Thu, 24 Jan 2013 14:24:15 -0500 X-RZG-AUTH: :P2EQZWCpfu+qG7CngxMFH1J+zrwiavkK6tmQaLfmwtM48/ll3c7qES2M X-RZG-CLASS-ID: mo00 Date: Thu, 24 Jan 2013 20:23:59 +0100 From: Olaf Hering To: "H. Peter Anvin" Cc: KY Srinivasan , Jan Beulich , "bp@alien8.de" , "apw@canonical.com" , "x86@kernel.org" , "tglx@linutronix.de" , "devel@linuxdriverproject.org" , "gregkh@linuxfoundation.org" , "jasowang@redhat.com" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts Message-ID: <20130124192359.GA22484@aepfle.de> References: <1358990259-22551-1-git-send-email-kys@microsoft.com> <5101035D02000078000B8FFD@nat28.tlf.novell.com> <27092660926e4d3f80394697cc0dc858@SN2PR03MB061.namprd03.prod.outlook.com> <51016C3202000078000B943E@nat28.tlf.novell.com> <20130124185943.GA19194@aepfle.de> <4d9be218-acf5-45a6-aeda-cee592fd74c8@email.android.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4d9be218-acf5-45a6-aeda-cee592fd74c8@email.android.com> User-Agent: Mutt/1.5.21.rev5632 (2013-01-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 24, H. Peter Anvin wrote: > Can't you discover Xen emulation by looking for Xen first? Or does Xen go "stealth"? The current code looks at cpuid to decide what the host type is. One thing to detect a Xen host is to look for the DIM strings, which still have "Xen HVM DomU" or similar. Olaf