All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Bernhard Kohl <bernhard.kohl@nsn.com>
Cc: kvm@vger.kernel.org, jan.kiszka@siemens.com
Subject: Re: [PATCH] Account for Fedora kernels with backported vzalloc
Date: Tue, 17 May 2011 20:30:04 +0300	[thread overview]
Message-ID: <4DD2B09C.5080208@redhat.com> (raw)
In-Reply-To: <1305644154-22027-1-git-send-email-bernhard.kohl@nsn.com>

On 05/17/2011 05:55 PM, Bernhard Kohl wrote:
> kvm-kmod-2.6.38.6 does not compile on Fedora kernels>= 2.6.35.11.

> index a40c39f..b91587c 100755
> --- a/configure
> +++ b/configure
> @@ -153,6 +153,13 @@ if [ -n "$no_uname" -a "$want_module" ]; then
>   	depmod_version=$kernel_version
>   fi
>
> +# Check if it is a Fedora kernel, e.g. 2.6.35.13-91.fc14.x86_64
> +if echo "$kernel_version" | grep -qE '[0-9.-]+\.fc[0-9]+\..+'; then
> +    config_fedora_kernel="#define CONFIG_FEDORA_KERNEL 1"
> +else
> +    config_fedora_kernel="#undef CONFIG_FEDORA_KERNEL"
> +fi
> +

Curious, why are you targetting Fedora kernels at all?  They have a 
really short shelf life.  I though kvm-kmod was for people using longer 
term kernels like enterprise distros or long lived embedded projects.

For Fedora, you can use the native kvm, or install a rawhide kernel, or 
an upstream kernel with 'make localmodconfig'.

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2011-05-17 17:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 14:55 [PATCH] Account for Fedora kernels with backported vzalloc Bernhard Kohl
2011-05-17 15:27 ` Jan Kiszka
2011-05-17 15:44   ` Kohl, Bernhard (NSN - DE/Munich)
2011-05-17 17:01     ` Jan Kiszka
2011-05-17 17:30 ` Avi Kivity [this message]
2011-05-18  9:11   ` Kohl, Bernhard (NSN - DE/Munich)
2011-05-18  9:20     ` 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=4DD2B09C.5080208@redhat.com \
    --to=avi@redhat.com \
    --cc=bernhard.kohl@nsn.com \
    --cc=jan.kiszka@siemens.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.