From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@alien8.de>, Dmitry Torokhov <dtor@vmware.com>,
Ingo Molnar <mingo@kernel.org>, X86 ML <x86@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
jasowang@redhat.com, Thomas Gleixner <tglx@linutronix.de>,
JBeulich@suse.com, "K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: [PATCH -v2 2/2] x86: Make Linux guest support optional
Date: Sat, 26 Jan 2013 17:26:40 -0800 [thread overview]
Message-ID: <51048250.6060108@zytor.com> (raw)
In-Reply-To: <20130125184356.GB4973@pd.tnic>
On 01/25/2013 10:43 AM, Borislav Petkov wrote:
> On Fri, Jan 25, 2013 at 07:35:07PM +0100, Borislav Petkov wrote:
>> Ok, if you prefer. We can definitely make all .o's which depend on
>> x86_hyper also depend on CONFIG_HYPERVISOR_GUEST - this solves the
>> whole deal trivially.
>>
>> I'll respin the patches.
>
> ... provided, of course, nothing out-of-tree is using x86_hyper. Can we
> assume that?
>
Out-of-tree code is responsible for keeping up, not the other way around.
-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-27 1:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 1:56 [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts 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:39 ` [PATCH 1/2] x86, Kconfig: Move PARAVIRT_DEBUG into the paravirt menu Borislav Petkov
2013-01-24 17:39 ` [PATCH 2/2] x86: Make Linux guest support optional Borislav Petkov
2013-01-25 8:21 ` [PATCH 1/2] x86, Kconfig: Move PARAVIRT_DEBUG into the paravirt menu Ingo Molnar
2013-01-25 8:51 ` Borislav Petkov
2013-01-25 9:20 ` Ingo Molnar
2013-01-25 9:29 ` Borislav Petkov
2013-01-25 9:32 ` Ingo Molnar
2013-01-25 10:06 ` Borislav Petkov
2013-01-25 17:59 ` [PATCH -v2 " Borislav Petkov
2013-01-25 17:59 ` [PATCH -v2 2/2] x86: Make Linux guest support optional Borislav Petkov
2013-01-25 18:07 ` Dmitry Torokhov
2013-01-25 18:23 ` Borislav Petkov
2013-01-25 18:29 ` Dmitry Torokhov
2013-01-25 18:35 ` Borislav Petkov
2013-01-25 18:43 ` Borislav Petkov
2013-01-27 1:26 ` H. Peter Anvin [this message]
2013-01-27 10:30 ` Borislav Petkov
2013-01-25 18:12 ` Dmitry Torokhov
2013-01-25 18:32 ` Borislav Petkov
2013-01-25 18:42 ` Dmitry Torokhov
2013-01-25 19:03 ` Borislav Petkov
2013-01-26 23:10 ` [PATCH -v3 1/2] x86, Kconfig: Move PARAVIRT_DEBUG into the paravirt menu Borislav Petkov
2013-01-26 23:10 ` [PATCH -v3 2/2] x86: Make Linux guest support optional Borislav Petkov
2013-01-27 11:06 ` Borislav Petkov
2013-01-28 10:18 ` [PATCH -v3.1] " Borislav Petkov
2013-01-24 17:42 ` [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts KY 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=51048250.6060108@zytor.com \
--to=hpa@zytor.com \
--cc=JBeulich@suse.com \
--cc=apw@canonical.com \
--cc=bp@alien8.de \
--cc=devel@linuxdriverproject.org \
--cc=dtor@vmware.com \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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