From: Gianluca Guida <gianluca.guida@eu.citrix.com>
To: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
Cc: Satoshi Moriai <moriai.satoshi@lab.ntt.co.jp>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Fix arguments passed to SHADOW_PRINTK
Date: Thu, 11 Sep 2008 11:49:05 +0100 [thread overview]
Message-ID: <48C8F7A1.7020309@eu.citrix.com> (raw)
In-Reply-To: <48C8F673.4070503@lab.ntt.co.jp>
Hi,
Yoshiaki Tamura wrote:
> Hi.
>
> When I compiled xen-3.3-testing with DEBUG_TRACE_DUMP in xen/include/xen/lib.h
> turned on, I got some errors at SHADOW_PRINTK.
> The following patch will fix the arguments passed to SHADOW_PRINTK in
> xen/arch/x86/mm/shadow/common.c and xen/arch/x86/mm/shadow/multi.c.
My fault, the va argument was removed with recent changes in the OOS
code and it is unneeded now.
> SHADOW_PRINTK("d=%d, v=%d, gmfn=%05lx, va=%lx\n",
> - v->domain->domain_id, v->vcpu_id, mfn_x(gmfn), va);
> + v->domain->domain_id, v->vcpu_id, mfn_x(gmfn),
> + sh_map_domain_page(gmfn));
>
> /* Need to pull write access so the page *stays* in sync. */
> if ( oos_remove_write_access(v, gmfn, fixup) )
> @@ -953,7 +954,8 @@ int sh_unsync(struct vcpu *v, mfn_t gmfn
> ASSERT(shadow_locked_by_me(v->domain));
>
> SHADOW_PRINTK("d=%d, v=%d, gmfn=%05lx va %lx\n",
> - v->domain->domain_id, v->vcpu_id, mfn_x(gmfn), va);
> + v->domain->domain_id, v->vcpu_id, mfn_x(gmfn),
> + sh_map_domain_page(gmfn));
These will likely break Xen in 32 bit, since you should unmap the gmfn
in those architecture. As I said, the va argument is unneeded now, so
you should remove it.
Thanks,
Gianluca
next prev parent reply other threads:[~2008-09-11 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 10:44 [PATCH] Fix arguments passed to SHADOW_PRINTK Yoshiaki Tamura
2008-09-11 10:49 ` Gianluca Guida [this message]
2008-09-11 11:00 ` Keir Fraser
2008-09-11 11:24 ` Yoshiaki Tamura
2008-09-11 11:42 ` Gianluca Guida
2008-09-11 11:56 ` Yoshiaki Tamura
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=48C8F7A1.7020309@eu.citrix.com \
--to=gianluca.guida@eu.citrix.com \
--cc=moriai.satoshi@lab.ntt.co.jp \
--cc=tamura.yoshiaki@lab.ntt.co.jp \
--cc=xen-devel@lists.xensource.com \
/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.