From: Avi Kivity <avi@redhat.com>
To: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: Move kvm_exit tracepoint rip reading inside tracepoint
Date: Thu, 11 Mar 2010 13:03:35 +0200 [thread overview]
Message-ID: <4B98CE07.2010804@redhat.com> (raw)
In-Reply-To: <4B98CDEF.4010003@oss.ntt.co.jp>
On 03/11/2010 01:03 PM, Takuya Yoshikawa wrote:
> Avi Kivity wrote:
>
>> diff --git a/arch/x86/kvm/trace.h b/arch/x86/kvm/trace.h
>> index b75efef..3cf9547 100644
>> --- a/arch/x86/kvm/trace.h
>> +++ b/arch/x86/kvm/trace.h
>> @@ -182,8 +182,8 @@ TRACE_EVENT(kvm_apic,
>> * Tracepoint for kvm guest exit:
>> */
>> TRACE_EVENT(kvm_exit,
>> - TP_PROTO(unsigned int exit_reason, unsigned long guest_rip),
>> - TP_ARGS(exit_reason, guest_rip),
>> + TP_PROTO(unsigned int exit_reason, struct kvm_vcpu *vcpu),
>>
> Whitespaces were inserted by accident?
>
Yeah, already fixed locally.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-03-11 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 8:52 [PATCH] KVM: Move kvm_exit tracepoint rip reading inside tracepoint Avi Kivity
2010-03-11 11:03 ` Takuya Yoshikawa
2010-03-11 11:03 ` 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=4B98CE07.2010804@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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