[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130124192359.GA22484@aepfle.de>
Date: Thu, 24 Jan 2013 20:23:59 +0100
From: Olaf Hering <olaf@...fle.de>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: KY Srinivasan <kys@...rosoft.com>, Jan Beulich <JBeulich@...e.com>,
"bp@...en8.de" <bp@...en8.de>,
"apw@...onical.com" <apw@...onical.com>,
"x86@...nel.org" <x86@...nel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as
special hypervisor interrupts
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists