From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Gleb Natapov <gleb@redhat.com>, kvm <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] kvm: Use kvm-kmod headers if available
Date: Tue, 12 Jan 2010 14:36:54 -0600 [thread overview]
Message-ID: <4B4CDD66.4030505@codemonkey.ws> (raw)
In-Reply-To: <4B4CC539.10306@siemens.com>
On 01/12/2010 12:53 PM, Jan Kiszka wrote:
> Since kvm-kmod-2.6.32.2 we have an alternative source for recent KVM
> kernel headers. Use it when available and not overruled by --kerneldir.
>
> Signed-off-by: Jan Kiszka<jan.kiszka@siemens.com>
>
Applied all. Thanks.
Regards,
Anthony Liguori
> ---
>
> Note: This is the upstream version first. qemu-kvm differs in this area,
> I will post corresponding patches for that tree later.
>
> configure | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/configure b/configure
> index 5c056f5..623c30e 100755
> --- a/configure
> +++ b/configure
> @@ -1384,7 +1384,7 @@ EOF
> kvm_cflags="$kvm_cflags -I$kerneldir/arch/$cpu/include"
> fi
> else
> - kvm_cflags=""
> + kvm_cflags=`pkg-config --cflags kvm-kmod 2> /dev/null`
> fi
> if compile_prog "$kvm_cflags" "" ; then
> kvm=yes
>
>
>
>
prev parent reply other threads:[~2010-01-12 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 18:53 [Qemu-devel] [PATCH 1/2] kvm: Use kvm-kmod headers if available Jan Kiszka
2010-01-12 20:20 ` [Qemu-devel] " Doug Goldstein
2010-01-12 21:22 ` Jan Kiszka
2010-01-12 20:36 ` Anthony Liguori [this message]
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=4B4CDD66.4030505@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.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).