From: Avi Kivity <avi@redhat.com>
To: Gui Jianfeng <guijianfeng@cn.fujitsu.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 2/3] KVM MMU: fix sp->unsync type error in trace event definition.
Date: Thu, 06 May 2010 12:24:21 +0300 [thread overview]
Message-ID: <4BE28AC5.50108@redhat.com> (raw)
In-Reply-To: <4BD01805.3050209@cn.fujitsu.com>
On 04/22/2010 12:33 PM, Gui Jianfeng wrote:
> sp->unsync is bool now, so update trace event declaration.
>
> Signed-off-by: Gui Jianfeng<guijianfeng@cn.fujitsu.com>
> ---
> arch/x86/kvm/mmutrace.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/kvm/mmutrace.h b/arch/x86/kvm/mmutrace.h
> index 3851f1f..9966e80 100644
> --- a/arch/x86/kvm/mmutrace.h
> +++ b/arch/x86/kvm/mmutrace.h
> @@ -11,7 +11,7 @@
> __field(__u64, gfn) \
> __field(__u32, role) \
> __field(__u32, root_count) \
> - __field(__u32, unsync)
> + __field(bool, unsync)
>
>
This was intended to be more or less binary compatible (well, mmutrace
not so much).
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-05-06 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 9:33 [PATCH 2/3] KVM MMU: fix sp->unsync type error in trace event definition Gui Jianfeng
2010-04-26 17:46 ` Marcelo Tosatti
2010-05-06 9:24 ` 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=4BE28AC5.50108@redhat.com \
--to=avi@redhat.com \
--cc=guijianfeng@cn.fujitsu.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.