From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751560Ab3AYHfJ (ORCPT ); Fri, 25 Jan 2013 02:35:09 -0500 Received: from nat28.tlf.novell.com ([130.57.49.28]:37320 "EHLO nat28.tlf.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750776Ab3AYHfH convert rfc822-to-8bit (ORCPT ); Fri, 25 Jan 2013 02:35:07 -0500 Message-Id: <510243B802000078000B9735@nat28.tlf.novell.com> X-Mailer: Novell GroupWise Internet Agent 12.0.1 Date: Fri, 25 Jan 2013 07:35:04 +0000 From: "Jan Beulich" To: "Olaf Hering" , "KY Srinivasan" Cc: "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" , "hpa@zytor.com" Subject: Re: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts 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> In-Reply-To: <20130124185943.GA19194@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >>> On 24.01.13 at 19:59, Olaf Hering wrote: > On Thu, Jan 24, KY Srinivasan wrote: > > >> > Question is - considering you stated that this is supported >> > starting in Win8, doesn't Hyper-V itself announce that >> > capability in some explicit way? >> >> Thanks Jan. Unfortunately I don't think tis interrupt delivery model >> is specified via a "feature" bit (I will check with the Windows guys). >> Perhaps, we can have a Hyper-V specific compilation switch to address >> the Xen emulation issue. > > Would that really help if both pvops XEN_PVHVM and HYPERV are enabled in > the config? I assume at this point the access to the DMI data is not yet > possible. As just said in another reply - with XEN_PVHVM, there's no problem, since Xen gets checked for first. There's only a problem when !XEN_PVHVM, because in that case Hyper-V will be probed for. And the problem can only get bigger when on top of that the out-of-tree PV drivers are intended to be used. Jan