From: Kevin Hilman <khilman@linaro.org>
To: Gleb Natapov <gleb@redhat.com>
Cc: Scott Wood <scottwood@freescale.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
linaro-kernel@lists.linaro.org,
Marcelo Tosatti <mtosatti@redhat.com>,
"open list\:KERNEL VIRTUAL MA..." <kvm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] KVM: allow host header to be included even for !CONFIG_KVM
Date: Thu, 21 Mar 2013 07:27:14 -0700 [thread overview]
Message-ID: <87ppyshlq5.fsf@linaro.org> (raw)
In-Reply-To: <20130321072955.GO3889@redhat.com> (Gleb Natapov's message of "Thu, 21 Mar 2013 09:29:55 +0200")
Gleb Natapov <gleb@redhat.com> writes:
> On Wed, Mar 20, 2013 at 06:58:41PM -0500, Scott Wood wrote:
>> On 03/14/2013 07:13:46 PM, Kevin Hilman wrote:
>> >The new context tracking subsystem unconditionally includes kvm_host.h
>> >headers for the guest enter/exit macros. This causes a compile
>> >failure when KVM is not enabled.
>> >
>> >Fix by adding an IS_ENABLED(CONFIG_KVM) check to kvm_host so it can
>> >be included/compiled even when KVM is not enabled.
>> >
>> >Cc: Frederic Weisbecker <fweisbec@gmail.com>
>> >Signed-off-by: Kevin Hilman <khilman@linaro.org>
>> >---
>> >Applies on v3.9-rc2
>> >
>> > include/linux/kvm_host.h | 7 ++++++-
>> > 1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> This broke the PPC non-KVM build, which was relying on stub
>> functions in kvm_ppc.h, which relies on "struct vcpu" in kvm_host.h.
>>
>> Why can't the entirety kvm_host.h be included regardless of
>> CONFIG_KVM, just like most other feature-specific headers? Why
>> can't the if/else just go around the functions that you want to stub
>> out for non-KVM builds?
>>
> Kevin,
>
> What compilation failure this patch fixes? I presume something ARM
> related.
Not specficially ARM related, but more context tracking related since
kernel/context_tracking.c pulls in kvm_host.h, which attempts to pull in
<asm/kvm*.h> which may not exist on some platforms.
At least for ARM, KVM support was added in v3.9 so this patch can
probably be dropped since the non-KVM builds on ARM now work. But any
platform without the <asm/kvm*.h> will still be broken when trying to
build the context tracker.
Kevin
next prev parent reply other threads:[~2013-03-21 14:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 0:13 [PATCH] KVM: allow host header to be included even for !CONFIG_KVM Kevin Hilman
2013-03-18 21:04 ` Marcelo Tosatti
2013-03-20 23:58 ` Scott Wood
2013-03-21 7:29 ` Gleb Natapov
2013-03-21 14:27 ` Kevin Hilman [this message]
2013-03-21 18:42 ` Scott Wood
2013-03-21 19:16 ` Gleb Natapov
2013-03-21 19:33 ` Scott Wood
2013-03-21 21:17 ` Gleb Natapov
2013-03-22 0:02 ` Kevin Hilman
2013-03-24 10:21 ` Gleb Natapov
2013-03-24 13:44 ` Frederic Weisbecker
2013-03-24 14:01 ` Gleb Natapov
2013-03-25 21:14 ` Kevin Hilman
2013-04-02 11:56 ` Gleb Natapov
2013-05-02 21:58 ` Alexander Graf
2013-05-15 22:52 ` Frederic Weisbecker
2013-05-17 1:04 ` Frederic Weisbecker
2013-05-17 14:09 ` Kevin Hilman
2013-05-17 14:34 ` Frederic Weisbecker
2013-05-17 17:00 ` Kevin Hilman
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=87ppyshlq5.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=fweisbec@gmail.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=scottwood@freescale.com \
/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