From: Frederic Weisbecker <fweisbec@gmail.com>
To: Kevin Hilman <khilman@linaro.org>
Cc: Gleb Natapov <gleb@redhat.com>,
Scott Wood <scottwood@freescale.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, 16 May 2013 00:52:03 +0200 [thread overview]
Message-ID: <20130515225201.GA2341@somewhere> (raw)
In-Reply-To: <87txnz9o7n.fsf@linaro.org>
On Mon, Mar 25, 2013 at 02:14:20PM -0700, Kevin Hilman wrote:
> Gleb Natapov <gleb@redhat.com> writes:
>
> > On Sun, Mar 24, 2013 at 02:44:26PM +0100, Frederic Weisbecker wrote:
> >> 2013/3/21 Gleb Natapov <gleb@redhat.com>:
> >> > Isn't is simpler for kernel/context_tracking.c to define empty
> >> > __guest_enter()/__guest_exit() if !CONFIG_KVM.
> >>
> >> That doesn't look right. Off-cases are usually handled from the
> >> headers, right? So that we avoid iffdeffery ugliness in core code.
> > Lets put it in linux/context_tracking.h header then.
>
> Here's a version to do that.
>
> Kevin
>
> From d9d909394479dd7ff90b7bddb95a564945406719 Mon Sep 17 00:00:00 2001
> From: Kevin Hilman <khilman@linaro.org>
> Date: Mon, 25 Mar 2013 14:12:41 -0700
> Subject: [PATCH v2] ontext_tracking: fix !CONFIG_KVM compile: add stub guest
> enter/exit
Sorry for my very delayed response...
>
> When KVM is not enabled, or not available on a platform, the KVM
> headers should not be included. Instead, just define stub
> __guest_[enter|exit] functions.
May be it would be cleaner to move guest_enter/exit definitions altogether
in linux/context_tracking.h
After all that's where the implementation mostly belong to.
Let me see if I can get that in shape.
Thanks.
next prev parent reply other threads:[~2013-05-15 22:52 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
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 [this message]
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=20130515225201.GA2341@somewhere \
--to=fweisbec@gmail.com \
--cc=gleb@redhat.com \
--cc=khilman@linaro.org \
--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