From: Avi Kivity <avi@redhat.com>
To: Dushyant Bansal <cs5070214@cse.iitd.ac.in>
Cc: Alexander Graf <agraf@suse.de>,
"<kvm-ppc@vger.kernel.org>" <kvm-ppc@vger.kernel.org>,
"qemu-devel@nongnu.org List" <qemu-devel@nongnu.org>
Subject: Re: qemu compiling error on ppc64: kvm.c:81: error: 'struct kvm_sregs'
Date: Wed, 16 Feb 2011 09:09:38 +0000 [thread overview]
Message-ID: <4D5B9452.4020305@redhat.com> (raw)
In-Reply-To: <4D5AA2C9.4030000@cse.iitd.ac.in>
On 02/15/2011 05:59 PM, Dushyant Bansal wrote:
>>> 2. How to configure makefiles to get output of printk statements
>>> inside kvm/arch/powerpc/kvm/trace.h
>> Better don't make them printks - just use the tracing framework. I'd
>> write up a small howto here myself, but I'm pretty much on the jump
>> to my plane for vacation. Avi, could you please guide him a bit on
>> how to get data out of tracepoints?
> Thanks for the quick reply :)
> I have added some more trace parameters in the tracing framework and
> currently, it is working fine.
> 1. Add new field in "struct kvm_vcpu_stat" (kvm_host.h)
> 2. Add corresponding entry in "struct kvm_stats_debugfs_item
> debugfs_entries[]" (book3s.c)
> 3. Increment or Decrement that field where ever necessary.
Those aren't tracepoints; they're deprecated debug statistics.
For tracepoints, see
include/trace/events/kvm.h (general kvm tracepoints)
arch/powerpc/kvm/trace.h (ppc specific tracepoints)
arch/powerpc/kvm/book3s_mmu_hpte.c (examples of use, look for
trace_kvm_*)
Documentation/trace/tracepoints.txt (documentation, likely outdated)
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Dushyant Bansal <cs5070214@cse.iitd.ac.in>
Cc: Alexander Graf <agraf@suse.de>,
"<kvm-ppc@vger.kernel.org>" <kvm-ppc@vger.kernel.org>,
"qemu-devel@nongnu.org List" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: qemu compiling error on ppc64: kvm.c:81: error: 'struct kvm_sregs' has no member named 'pvr'
Date: Wed, 16 Feb 2011 11:09:38 +0200 [thread overview]
Message-ID: <4D5B9452.4020305@redhat.com> (raw)
In-Reply-To: <4D5AA2C9.4030000@cse.iitd.ac.in>
On 02/15/2011 05:59 PM, Dushyant Bansal wrote:
>>> 2. How to configure makefiles to get output of printk statements
>>> inside kvm/arch/powerpc/kvm/trace.h
>> Better don't make them printks - just use the tracing framework. I'd
>> write up a small howto here myself, but I'm pretty much on the jump
>> to my plane for vacation. Avi, could you please guide him a bit on
>> how to get data out of tracepoints?
> Thanks for the quick reply :)
> I have added some more trace parameters in the tracing framework and
> currently, it is working fine.
> 1. Add new field in "struct kvm_vcpu_stat" (kvm_host.h)
> 2. Add corresponding entry in "struct kvm_stats_debugfs_item
> debugfs_entries[]" (book3s.c)
> 3. Increment or Decrement that field where ever necessary.
Those aren't tracepoints; they're deprecated debug statistics.
For tracepoints, see
include/trace/events/kvm.h (general kvm tracepoints)
arch/powerpc/kvm/trace.h (ppc specific tracepoints)
arch/powerpc/kvm/book3s_mmu_hpte.c (examples of use, look for
trace_kvm_*)
Documentation/trace/tracepoints.txt (documentation, likely outdated)
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-02-16 9:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 13:25 [Qemu-devel] qemu compiling error on ppc64: kvm.c:81: error: struct kvm_sregs has no member named pvr Dushyant Bansal
2011-02-04 13:37 ` qemu compiling error on ppc64: kvm.c:81: error: Dushyant Bansal
2011-02-04 14:43 ` Alexander Graf
2011-02-04 14:43 ` [Qemu-devel] Re: qemu compiling error on ppc64: kvm.c:81: error: struct kvm_sregs has no member named pvr Alexander Graf
2011-02-04 18:35 ` qemu compiling error on ppc64: kvm.c: Jan Kiszka
2011-02-04 18:35 ` [Qemu-devel] Re: qemu compiling error on ppc64: kvm.c:81: error: struct kvm_sregs has no member named pvr Jan Kiszka
2011-02-04 20:03 ` qemu compiling error on ppc64: kvm.c:81: error: Alexander Graf
2011-02-04 20:03 ` [Qemu-devel] Re: qemu compiling error on ppc64: kvm.c:81: error: struct kvm_sregs has no member named pvr Alexander Graf
2011-02-04 19:19 ` Dushyant Bansal
2011-02-04 19:31 ` qemu compiling error on ppc64: kvm.c: Dushyant Bansal
2011-02-04 20:04 ` qemu compiling error on ppc64: kvm.c:81: error: Alexander Graf
2011-02-04 20:04 ` [Qemu-devel] Re: qemu compiling error on ppc64: kvm.c:81: error: struct kvm_sregs has no member named pvr Alexander Graf
2011-02-15 14:21 ` Dushyant Bansal
2011-02-15 14:33 ` qemu compiling error on ppc64: kvm.c: Dushyant Bansal
2011-02-15 14:33 ` Alexander Graf
2011-02-15 14:33 ` [Qemu-devel] Re: qemu compiling error on ppc64: kvm.c:81: error: struct kvm_sregs has no member named pvr Alexander Graf
2011-02-15 15:59 ` [Qemu-devel] Re: qemu compiling error on ppc64: kvm.c:81: error: 'struct kvm_sregs' has no member named 'pvr' Dushyant Bansal
2011-02-15 16:11 ` qemu compiling error on ppc64: kvm.c:81: error: 'struct kvm_sregs' Dushyant Bansal
2011-02-16 9:09 ` Avi Kivity [this message]
2011-02-16 9:09 ` [Qemu-devel] Re: qemu compiling error on ppc64: kvm.c:81: error: 'struct kvm_sregs' has no member named 'pvr' Avi Kivity
2011-02-25 16:17 ` Dushyant Bansal
2011-02-25 16:29 ` qemu compiling error on ppc64: kvm.c:81: error: 'struct kvm_sregs' Dushyant Bansal
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=4D5B9452.4020305@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=cs5070214@cse.iitd.ac.in \
--cc=kvm-ppc@vger.kernel.org \
--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 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.