qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Dushyant Bansal <cs5070214@cse.iitd.ac.in>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-devel@nongnu.org List" <qemu-devel@nongnu.org>,
	"<kvm-ppc@vger.kernel.org>" <kvm-ppc@vger.kernel.org>,
	Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] Re: qemu compiling error on ppc64: kvm.c:81: error: 'struct kvm_sregs' has no member named 'pvr'
Date: Tue, 15 Feb 2011 21:29:05 +0530	[thread overview]
Message-ID: <4D5AA2C9.4030000@cse.iitd.ac.in> (raw)
In-Reply-To: <683A1DC5-CC47-492B-AEC0-29795890CEE8@suse.de>

On Tuesday 15 February 2011 08:03 PM, Alexander Graf wrote:
> On 15.02.2011, at 15:21, Dushyant Bansal wrote:
>
>    
>>      
>>>>> Hrm. This means that your kernel headers in /usr/include/linux are too old. Can you try and find out which kernel version they are from please
>>>>>
>>>>>
>>>>>            
>>>> Yes, kernel headers version is 2.6.32. For the time being, I copied some of the header files from kvm/arch/powerpc/include/asm/ to kernel headers and qemu build was successful.
>>>> Thanks a lot.
>>>>
>>>>          
>>> Awesome! I'm eager to hear how well it works for you :)
>>>        
>> I collected some performance stats using kvm_stat. To get more information about exit counts of individual instructions, I configured CFLAGS_emulate.o with DDEBUG flag.
>> Now, I can see output of  "pr_debug("Emulating opcode %d / %d\n", get_op(inst), get_xop(inst));" instruction in kernel logs.
>> I have two queries:
>>
>> 1. The count of "Emulating opcode...." statement in /var/log/kern.log (3 million) is coming out to be much less than emulated_inst_exits (22 million) using kvm_stat.
>>      
> The kernel log ring buffer is probably faster filled than read :).
>
>    
>> 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.

I can see stats for the new parameter in kvm_stat output. I guess, this 
approach is okay.

> This means exactly what it means. There are two possible causes:
>
> 1) Your kernel is too old and doesn't support the capability
> 2) Qemu was compiled with kernel headers that don't know the capability yet
>
> If it's 2, just copy some of the kvm*.h files from your kernel source over to /usr/include/linux or /usr/include/asm-powerpc and fix them up to compile (remove __user).
>
>    
I think, its reason 2. I'll try this.


Thanks,
Dushyant

  reply	other threads:[~2011-02-15 16:02 UTC|newest]

Thread overview: 11+ 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 14:43 ` [Qemu-devel] " Alexander Graf
2011-02-04 18:35   ` Jan Kiszka
2011-02-04 20:03     ` Alexander Graf
2011-02-04 19:19   ` Dushyant Bansal
2011-02-04 20:04     ` Alexander Graf
2011-02-15 14:21       ` Dushyant Bansal
2011-02-15 14:33         ` Alexander Graf
2011-02-15 15:59           ` Dushyant Bansal [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

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=4D5AA2C9.4030000@cse.iitd.ac.in \
    --to=cs5070214@cse.iitd.ac.in \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --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 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).