From: Stefan Weil <weil@mail.berlios.de>
To: Alexander Graf <agraf@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
QEMU-devel Developers <qemu-devel@nongnu.org>,
Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/6] xen: add mapcache stubs
Date: Wed, 20 Jul 2011 18:41:31 +0200 [thread overview]
Message-ID: <4E27053B.7080804@mail.berlios.de> (raw)
In-Reply-To: <1311044012-24288-3-git-send-email-agraf@suse.de>
Am 19.07.2011 04:53, schrieb Alexander Graf:
> 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.
>
> This patch adds the stubs again - this time in the generic xen-stubs.c
>
> Signed-off-by: Alexander Graf <agraf@suse.de>
> ---
> xen-stub.c | 26 ++++++++++++++++++++++++++
> 1 files changed, 26 insertions(+), 0 deletions(-)
>
> diff --git a/xen-stub.c b/xen-stub.c
> index efe2ab5..76d80e9 100644
> --- a/xen-stub.c
> +++ b/xen-stub.c
> @@ -8,6 +8,7 @@
>
> #include "qemu-common.h"
> #include "hw/xen.h"
> +#include "xen-mapcache.h"
>
> void xenstore_store_pv_console_info(int i, CharDriverState *chr)
> {
> @@ -43,3 +44,28 @@ int xen_init(void)
> {
> return -ENOSYS;
> }
> +
> +/******* mapcache stubs *******/
> +
> +void xen_map_cache_init(void)
> +{
> +}
> +
> +uint8_t *xen_map_cache(target_phys_addr_t phys_addr,
> target_phys_addr_t size,
> + uint8_t lock)
> +{
> + return qemu_get_ram_ptr(phys_addr);
> +}
> +
> +ram_addr_t xen_ram_addr_from_mapcache(void *ptr)
> +{
> + return -1;
> +}
> +
> +void xen_invalidate_map_cache(void)
> +{
> +}
> +
> +void xen_invalidate_map_cache_entry(uint8_t *buffer)
> +{
> +}
The patch fixes a build problem, and the sooner we fix it,
the better it is.
Do we really need a return value other than NULL in xen_map_cache()?
Do we need the stubs for xen_map_cache_init() and
xen_invalidate_map_cache()?
As discussed in another thread, static inline stub function might be better.
Regards,
Stefan W.
next prev parent reply other threads:[~2011-07-20 16:41 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
2011-07-20 15:24 ` Alexander Graf
2011-07-20 16:41 ` Stefan Weil [this message]
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=4E27053B.7080804@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=avi@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).