From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Chris Clayton <chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: building kvm-31 against linux-2.6.22-git16
Date: Sun, 22 Jul 2007 12:43:25 +0300 [thread overview]
Message-ID: <46A326BD.2030201@qumranet.com> (raw)
In-Reply-To: <200707211126.32042.chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Chris Clayton wrote:
> Hi,
>
> Due to changes to kmem_cache_create, kvm-31 fails to build against
> linux-2.6.22-git16:
>
> CC [M] /home/users/chris/rpm/BUILD/kvm-31/kernel/vmx-debug.o
> CC [M] /home/users/chris/rpm/BUILD/kvm-31/kernel/kvm_main.o
> CC [M] /home/users/chris/rpm/BUILD/kvm-31/kernel/mmu.o
> /home/users/chris/rpm/BUILD/kvm-31/kernel/mmu.c: In
> function 'kvm_mmu_module_init':
> /home/users/chris/rpm/BUILD/kvm-31/kernel/mmu.c:1314: error: too many
> arguments to function 'kmem_cache_create'
> /home/users/chris/rpm/BUILD/kvm-31/kernel/mmu.c:1319: error: too many
> arguments to function 'kmem_cache_create'
> /home/users/chris/rpm/BUILD/kvm-31/kernel/mmu.c:1325: error: too many
> arguments to function 'kmem_cache_create'
> /home/users/chris/rpm/BUILD/kvm-31/kernel/mmu.c:1331: error: too many
> arguments to function 'kmem_cache_create'
> make[3]: *** [/home/users/chris/rpm/BUILD/kvm-31/kernel/mmu.o] Error 1
>
>
> The patch below fixes this:
>
> --- kvm-31/kernel/mmu.c~ 2007-07-21 11:12:45.000000000 +0000
> +++ kvm-31/kernel/mmu.c 2007-07-21 11:14:09.000000000 +0000
> @@ -1311,24 +1311,24 @@
> {
> pte_chain_cache = kmem_cache_create("kvm_pte_chain",
> sizeof(struct kvm_pte_chain),
> - 0, 0, NULL, NULL);
> + 0, 0, NULL);
>
This has already been fixed in mainline. I added some hacks so kvm-32
will be buildable both on 2.6.23-rc1 and on 2.6.22 (but not on
2.6.22-git16).
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
prev parent reply other threads:[~2007-07-22 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 11:26 building kvm-31 against linux-2.6.22-git16 Chris Clayton
[not found] ` <200707211126.32042.chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2007-07-22 9:43 ` Avi Kivity [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=46A326BD.2030201@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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