From: "H. Peter Anvin" <firstname.lastname@example.org> To: KY Srinivasan <email@example.com> Cc: Jan Beulich <JBeulich@suse.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> Subject: Re: [PATCH 2/3] X86: Add a check to catch Xen emulation of Hyper-V Date: Wed, 30 Jan 2013 10:19:06 -0800 [thread overview] Message-ID: <5109641A.firstname.lastname@example.org> (raw) In-Reply-To: <1db4d98aa3434d4eab7b36bbeb89cd47@SN2PR03MB061.namprd03.prod.outlook.com> On 01/30/2013 10:12 AM, KY Srinivasan wrote: >> >> I'm not convinced that's the right approach - any hypervisor >> could do similar emulation, and hence you either want to make >> sure you run on Hyper-V (by excluding all others), or you >> tolerate using the emulation (which may require syncing up with >> the other guest implementations so that shared resources don't >> get used by two parties). >> >> I also wonder whether using the Hyper-V emulation (where >> useful, there might not be anything right now, but this may >> change going forward) when no Xen support is configured >> wouldn't be better than not using anything... > > Jan, > > Presumably, Hyper-V emulation is only to run enlightened Windows. The issue with > Xen is not that it emulates Hyper-V, but this emulation is turned on while running Linux. > That is the reason I chose to check for Xen. Would you prefer a DMI check for the Hyper-V > platform. > The real issue here is anyone going to run a kernel: 1. which has Xen support *disabled*, 2. which has HyperV support *enabled*, 3. on top of Xen, 4. with Xen HyperV support enabled. The fundamental problem seems to be that Xen HyperV support is "just good enough to run Windows", but in fact has some serious shortcomings which breaks Linux guests that don't have Xen support (if they do, the Xen support kicks in instead.) Am I right? -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2013-01-30 18:20 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 [this message] 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 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=5109641A.email@example.com \ --firstname.lastname@example.org \ --cc=JBeulich@suse.com \ --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' \ /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).