kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 0/4] Allow enabling kvm_trace on external module
Date: Wed, 24 Sep 2008 14:26:07 -0300	[thread overview]
Message-ID: <20080924172607.GO11604@blackpad> (raw)
In-Reply-To: <48DA4533.6040303@redhat.com>

On Wed, Sep 24, 2008 at 04:48:35PM +0300, Avi Kivity wrote:
> Eduardo Habkost wrote:
>> This series adds compat code to allow enabling kvm_trace when building
>> KVM as an external module on older kernels.
>>
>> The most hackish part is the last patch, that adds --with-kvm-trace to
>> configure and adds an include to a generated file on kernel/x86/Kbuild. It
>> doesn't look pretty, so suggestions on how to make this better are
>> welcome.
>>   
>
> Applied all, thanks.  We could improve Kbuild by having kernel/Makefile  
> include config.mak and pass some variable to Kbuild somehow, but diving  
> into Kbuild isn't my idea of a week well spent.

Oops. I've just noticed I broke './configure --with-patched-kernel'. Fix below.

---
From: Eduardo Habkost <ehabkost@redhat.com>
Date: Wed, 24 Sep 2008 14:11:42 -0300
Subject: Always generate config.kbuild

When implementing --with-kvm-trace, I supposed make would never enter
the 'kernel' directory when compiling with --with-patched-kernel. I was
wrong and broke --with-patched-kernel.

Change configure to always generate config.kbuild on the kernel
directory. Otherwise make will explode on 'make header-sync', that runs
even when --with-patched-kernel was used.

Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
---
 configure |    2 --
 1 files changed, 0 insertions(+), 2 deletions(-)

diff --git a/configure b/configure
index 78c2f9c..3b27364 100755
--- a/configure
+++ b/configure
@@ -137,8 +137,6 @@ LD=$cross_prefix$ld
 OBJCOPY=$cross_prefix$objcopy
 EOF
 
-if [ -n "$want_module" ];then
 cat <<EOF > kernel/config.kbuild
 CONFIG_KVM_TRACE=$kvm_trace
 EOF
-fi
-- 
1.5.5.GIT


-- 
Eduardo

  reply	other threads:[~2008-09-24 17:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 17:52 [PATCH 0/4] Allow enabling kvm_trace on external module Eduardo Habkost
2008-09-22 17:52 ` [PATCH 1/4] Add kvm_trace.c to hack-files-x86 Eduardo Habkost
2008-09-22 17:52 ` [PATCH 2/4] Hack DEFINE_SIMPLE_ATTRIBUTE for lost_records_get() also Eduardo Habkost
2008-09-22 17:52 ` [PATCH 3/4] relay_open() compat Eduardo Habkost
2008-09-24 13:50   ` Avi Kivity
2008-09-22 17:52 ` [PATCH 4/4] Add --with-kvm-trace arg to configure Eduardo Habkost
2008-09-24 13:48 ` [PATCH 0/4] Allow enabling kvm_trace on external module Avi Kivity
2008-09-24 17:26   ` Eduardo Habkost [this message]
2008-09-25 11:25     ` Avi Kivity

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=20080924172607.GO11604@blackpad \
    --to=ehabkost@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.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;
as well as URLs for NNTP newsgroup(s).