Kernel KVM-PPC virtualization development
 help / color / mirror / Atom feed
From: Dushyant Bansal <cs5070214@cse.iitd.ac.in>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>
Subject: Re: qemu compiling error on ppc64: kvm.c:
Date: Tue, 15 Feb 2011 14:33:15 +0000	[thread overview]
Message-ID: <4D5A8BDB.1000206@cse.iitd.ac.in> (raw)
In-Reply-To: <7703D057-F12D-4B95-9AEE-190C4EB2A3CE@suse.de>


>>> 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.

2. How to configure makefiles to get output of printk statements inside 
kvm/arch/powerpc/kvm/trace.h

Also, every time I start kvm, I get this error "KVM: Couldn't find level 
irq capability. Expect the VM to stall at times". After some time, the 
VM just hangs. I traced this output to qemu/target-ppc/kvm.c Is there 
any way to avoid it.

Thanks,
Dushyant

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 18:35   ` qemu compiling error on ppc64: kvm.c: Jan Kiszka
2011-02-04 20:03     ` qemu compiling error on ppc64: kvm.c:81: error: Alexander Graf
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-15 14:33       ` Dushyant Bansal [this message]
2011-02-15 14:33         ` qemu compiling error on ppc64: kvm.c: Alexander Graf
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
2011-02-25 16:29               ` 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=4D5A8BDB.1000206@cse.iitd.ac.in \
    --to=cs5070214@cse.iitd.ac.in \
    --cc=agraf@suse.de \
    --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