public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: KVM mailing list <kvm@vger.kernel.org>
Subject: [PATCH + RFC] Cascading option --with-kvm-trace to qemu configure script
Date: Tue, 26 May 2009 21:40:14 -0300	[thread overview]
Message-ID: <1243384814.2858.55.camel@localhost.localdomain> (raw)

We've found a build issue on release tarballs: if we take a recent
release tarball, build it using the usual sequence

./configure
make
make install

The modules generated can't be loaded due to unresolved symbols related
to kvm trace. While fixing the problem, we noticed that is not possible
to pass the --with-kvm-trace option to the main qemu configure script.

This patch makes it possible to cascade --with-kvm-trace option from the
qemu toplevel configure script to the KVM kernel configure script. It is
our understanding that this cascading is desirable, however we are not
completely sure about it, hence we are asking for comments on this
change.

The actual fix for the issue we found will follow, however the patches
are independant.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>

--- configure	2009-05-19 13:29:02.000000000 -0300
+++ ../configure.backup	2009-05-26 21:16:53.702104650 -0300
@@ -198,6 +198,7 @@
 mixemu="no"
 bluez="yes"
 kvm="yes"
+kvm_trace="no"
 kvm_cap_pit="no"
 kvm_cap_device_assignment="no"
 kerneldir=""
@@ -521,6 +522,8 @@
   ;;
   --kerneldir=*) kerneldir="$optarg"
   ;;
+  --with-kvm-trace) kvm_trace="yes"
+  ;;
   --with-pkgversion=*) pkgversion=" ($optarg)"
   ;;
   --disable-cpu-emulation) cpu_emulation="no"
@@ -656,6 +659,7 @@
 echo "  --enable-io-thread       enable IO thread"
 echo "  --disable-blobs          disable installing provided firmware blobs"
 echo "  --kerneldir=PATH         look for kernel includes in PATH"
+echo "  --with-kvm-trace         enable building the KVM module with the kvm trace option"
 echo "  --disable-cpu-emulation  disables use of qemu cpu emulation code"
 echo ""
 echo "NOTE: The object files are built at the place where configure is launched"
@@ -1402,7 +1406,10 @@
     kvm_kmod="yes"
     kmod_args=""
     if test -n "$kerneldir"; then
-	kmod_args="--kerneldir=$kerneldir"
+        kmod_args="--kerneldir=$kerneldir"
+    fi
+    if test "$kvm_trace" = "yes"; then
+        kmod_args="$kmod_args --with-kvm-trace"
     fi
     # hope there are no spaces in kmod_args; can't use arrays because of
     # dash.
@@ -1470,6 +1477,7 @@
 echo "IO thread         $io_thread"
 echo "Install blobs     $blobs"
 echo "KVM support       $kvm"
+echo "KVM trace support $kvm_trace"
 echo "fdt support       $fdt"
 echo "preadv support    $preadv"
 





-- 
Lucas Meneghel Rodrigues
Software Engineer (QE)
Red Hat - Emerging Technologies


             reply	other threads:[~2009-05-27  0:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27  0:40 Lucas Meneghel Rodrigues [this message]
2009-05-31 11:21 ` [PATCH + RFC] Cascading option --with-kvm-trace to qemu configure script 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=1243384814.2858.55.camel@localhost.localdomain \
    --to=lmr@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