From: "H. Peter Anvin" <hpa@zytor.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: KY Srinivasan <kys@microsoft.com>,
Jan Beulich <JBeulich@suse.com>, "bp@alien8.de" <bp@alien8.de>,
"apw@canonical.com" <apw@canonical.com>,
"x86@kernel.org" <x86@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts
Date: Thu, 24 Jan 2013 13:30:52 -0600 [thread overview]
Message-ID: <e8da7a46-c0f6-4590-87a4-e9860fb4ccab@email.android.com> (raw)
In-Reply-To: <20130124192359.GA22484@aepfle.de>
And there is no evidence of Xen in CPUID?
Olaf Hering <olaf@aepfle.de> wrote:
>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
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
next prev parent reply other threads:[~2013-01-24 19:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 1:17 K. Y. Srinivasan
2013-01-24 8:48 ` Jan Beulich
2013-01-24 16:07 ` KY Srinivasan
2013-01-24 16:15 ` Jan Beulich
2013-01-24 18:48 ` KY Srinivasan
2013-01-24 18:59 ` Olaf Hering
2013-01-24 19:03 ` KY Srinivasan
2013-01-25 7:32 ` Jan Beulich
2013-01-24 19:04 ` H. Peter Anvin
2013-01-24 19:23 ` Olaf Hering
2013-01-24 19:30 ` H. Peter Anvin [this message]
2013-01-25 7:30 ` Jan Beulich
2013-01-25 7:35 ` Jan Beulich
2013-01-25 13:58 ` Olaf Hering
2013-01-24 19:10 ` H. Peter Anvin
2013-01-25 7:31 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2013-01-24 1:56 K. Y. Srinivasan
2013-01-24 9:28 ` Borislav Petkov
2013-01-24 12:11 ` H. Peter Anvin
2013-01-24 17:35 ` Borislav Petkov
2013-01-24 17:36 ` H. Peter Anvin
2013-01-24 17:42 ` KY Srinivasan
2013-01-18 1:55 K. Y. Srinivasan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e8da7a46-c0f6-4590-87a4-e9860fb4ccab@email.android.com \
--to=hpa@zytor.com \
--cc=JBeulich@suse.com \
--cc=apw@canonical.com \
--cc=bp@alien8.de \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome