From: "Jan Beulich" <JBeulich@suse.com> To: "KY Srinivasan" <firstname.lastname@example.org> Cc: "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org> Subject: RE: [PATCH 2/3] X86: Add a check to catch Xen emulation of Hyper-V Date: Thu, 31 Jan 2013 16:45:34 +0000 [thread overview] Message-ID: <510AADBE02000078000BB190@nat28.tlf.novell.com> (raw) In-Reply-To: <fe91cec766464b4fbfeea56d7e5de0a0@SN2PR03MB061.namprd03.prod.outlook.com> >>> On 31.01.13 at 16:53, KY Srinivasan <email@example.com> wrote: > Are there any published standards in terms of how the CPUID space should be > populated in the range from 0x40000000 to 0x40010000. Specifically, unless I recall having seen this range being marked as reserved for hypervisor use somewhere, but I don't remember where that was. > the standard mandates that all ranges unused by a given hypervisor would > return a known value, how can this code be used to detect the presence of an > unknown hypervisor. Hyper-V is going to return the Hyper-V string at > 0x40000000. So, I was planning to scan starting at 0x40000100. Clearly, I can > check for a specific hypervisor that I know causes a problem for Hyper-V (as I > have currently done by checking for Xen). How can I check for the presence of > yet to be created Hypervisors that may emulate Hyper-V by scanning the CPUID > space. I am almost tempted to say that Xen is the special case and the patch > I have submitted addresses that. If a new (or existing hypervisor) plans to > do what Xen is doing, perhaps we can dissuade them from doing that or we can > fix that within the general framework we have here. I'd simply preset ECX, EDX, and EBX to zero, and check whether they change on any EAX input divisible by 256, skipping the one range you know Hyper-V sits in. Jan
next prev parent reply other threads:[~2013-01-31 16:45 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-30 0:51 [PATCH 0/3] X86: Deliver Hyper-V interrupts on a seperate IDT vector K. Y. Srinivasan 2013-01-30 0:51 ` [PATCH 1/3] x86: Hyper-V: register clocksource only if its advertised K. Y. Srinivasan 2013-01-30 0:51 ` [PATCH 2/3] X86: Add a check to catch Xen emulation of Hyper-V K. Y. Srinivasan 2013-01-30 8:53 ` Jan Beulich 2013-01-30 18:12 ` KY Srinivasan 2013-01-30 18:19 ` H. Peter Anvin 2013-01-31 7:37 ` Jan Beulich 2013-01-31 14:46 ` KY Srinivasan 2013-01-31 15:53 ` KY Srinivasan 2013-01-31 16:45 ` Jan Beulich [this message] 2013-01-31 18:29 ` H. Peter Anvin 2013-01-31 21:41 ` H. Peter Anvin 2013-02-01 13:19 ` Stefano Stabellini 2013-02-01 15:10 ` KY Srinivasan 2013-02-01 19:34 ` KY Srinivasan 2013-01-30 0:51 ` [PATCH 3/3] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts K. Y. Srinivasan 2013-01-30 8:58 ` Jan Beulich 2013-01-31 14:55 ` KY Srinivasan 2013-02-04 1:21 [PATCH 0/3] X86: Deliver Hyper-V interrupts on a seperate IDT vector K. Y. Srinivasan 2013-02-04 1:22 ` [PATCH 1/3] x86: Hyper-V: register clocksource only if its advertised K. Y. Srinivasan 2013-02-04 1:22 ` [PATCH 2/3] X86: Add a check to catch Xen emulation of Hyper-V K. Y. Srinivasan 2013-04-17 7:06 ` Michael S. Tsirkin 2013-04-17 13:20 ` KY Srinivasan 2013-04-17 12:48 ` Michael S. Tsirkin 2013-04-17 14:12 ` KY Srinivasan 2013-04-17 13:25 ` Michael S. Tsirkin 2013-04-17 14:34 ` KY Srinivasan 2013-04-17 13:48 ` Michael S. Tsirkin 2013-04-17 15:31 ` KY Srinivasan 2013-04-17 15:50 ` Jan Beulich 2013-04-17 16:28 ` KY Srinivasan 2013-04-18 7:48 ` Michael S. Tsirkin 2013-04-18 13:23 ` KY Srinivasan 2013-04-18 13:30 ` KY Srinivasan 2013-04-17 13:52 ` Jan Beulich 2013-04-17 13:01 ` Michael S. Tsirkin 2013-04-17 13:11 ` Michael S. Tsirkin 2013-04-17 14:09 ` Jan Beulich 2013-04-17 15:17 ` H. Peter Anvin
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=510AADBE02000078000BB190@nat28.tlf.novell.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='RE: [PATCH 2/3] X86: Add a check to catch Xen emulation of Hyper-V' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).