From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
QEMU-devel Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 2/6] xen: add mapcache stubs
Date: Wed, 20 Jul 2011 18:12:16 +0300 [thread overview]
Message-ID: <4E26F050.9090508@redhat.com> (raw)
In-Reply-To: <1311044012-24288-3-git-send-email-agraf@suse.de>
On 07/19/2011 05:53 AM, Alexander Graf wrote:
> During the transition to get rid of CONFIG_XEN_MAPCACHE we lost the mapcache
> stubs along the way. Nobody realized it because the commands were guarded by
> if (xen_enabled()) clauses that made gcc optimize out the respective calls.
>
Except those building with --enable-debug.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-07-20 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 2:53 [Qemu-devel] [PATCH 0/6] Xen patch queue 2011-07-20 Alexander Graf
2011-07-19 2:53 ` [Qemu-devel] [PATCH 1/6] xen: introduce xen_change_state_handler Alexander Graf
2011-07-19 2:53 ` [Qemu-devel] [PATCH 2/6] xen: add mapcache stubs Alexander Graf
2011-07-20 15:12 ` Avi Kivity [this message]
2011-07-20 15:24 ` Alexander Graf
2011-07-20 16:41 ` Stefan Weil
2011-07-20 16:45 ` Alexander Graf
2011-07-19 2:53 ` [Qemu-devel] [PATCH 3/6] xen: Fix xen_enabled() Alexander Graf
2011-07-19 2:53 ` [Qemu-devel] [PATCH 4/6] exec.c: Use ram_addr_t in cpu_physical_memory_rw(...) Alexander Graf
2011-07-19 2:53 ` [Qemu-devel] [PATCH 5/6] xen: remove CONFIG_XEN_MAPCACHE Alexander Graf
2011-07-19 2:53 ` [Qemu-devel] [PATCH 6/6] xen: make xen_enabled even more clever Alexander Graf
2011-07-20 15:10 ` [Qemu-devel] [PATCH 0/6] Xen patch queue 2011-07-20 Alexander Graf
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=4E26F050.9090508@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.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).