All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: KVM list <kvm@vger.kernel.org>,
	nikola.ciprich@linuxbox.cz,
	"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: qemu-kvm-0.13.0 - winsows 2008 - chkdisk too slow
Date: Thu, 06 Jan 2011 12:19:21 +0200	[thread overview]
Message-ID: <4D259729.2050403@redhat.com> (raw)
In-Reply-To: <20110106094240.GE17772@pcnci.linuxbox.cz>

On 01/06/2011 11:42 AM, Nikola Ciprich wrote:
> >  - run trace-cmd record -e kvm -b 100000 -P pid1 -P pid2, ctrl-C after a
> seems like it's not possible to specify multiple pids, so

Did you get 'overrun: something' reports from trace-cmd, where something 
!= 0?

If you're not sure, please run the trace again.  Also try adding '-r 10' 
to the command line.

> I've run 4 commands in parallel. Also I can't get monitor information
> since vm is started using libvirt, so I've just used all machine's qemu-kvm
> pids..

Dan, is there a way to hijack the monitor so we can run some commands on 
it?  Things like 'info registers' and disassembly.

> hope it's OK
> here's the trace:
> http://nelide.cz/downloads/nik/trace.tar.bz2
> n.
>

Looks like vcpu 1 is spinning; perhaps that's normal.  If you get hold 
of the monitor, please disassemble around 0xfffff80001575d59.

vcpu 0 is busy writing to vga (can you confirm)? looks like bank 
switching is hitting synchronize_srcu_expedited(), which is known slow.  
Unfortunately that only gets better in 2.6.38.

You can try applying 
http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git;a=commit;h=46fdb0937f26124700fc9fc80da4776330cc00d3 
and see if it helps.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2011-01-06 10:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06  7:48 qemu-kvm-0.13.0 - winsows 2008 - chkdisk too slow Nikola Ciprich
2011-01-06  9:03 ` Stefan Hajnoczi
2011-01-06  9:06   ` Nikola Ciprich
2011-01-06  9:08 ` Avi Kivity
2011-01-06  9:20   ` Nikola Ciprich
2011-01-06  9:27     ` Avi Kivity
2011-01-06  9:30       ` Avi Kivity
2011-01-06  9:42       ` Nikola Ciprich
2011-01-06 10:19         ` Avi Kivity [this message]
2011-01-06 10:25           ` Nikola Ciprich
2011-01-06 10:50             ` Avi Kivity
2011-01-06 11:06           ` Daniel P. Berrange
2011-01-06 12:19             ` Nikola Ciprich
2011-01-06 12:18           ` Nikola Ciprich
2011-01-06 13:26             ` Avi Kivity
2011-01-06 13:55               ` Nikola Ciprich
2011-01-06 14:37                 ` Avi Kivity
2011-01-06 15:38                   ` Nikola Ciprich
2011-01-09 12:36                     ` Nikola Ciprich
2011-01-09 12:39                       ` Avi Kivity
2011-01-09 13:36                         ` Nikola Ciprich
2011-01-09 13:44                           ` Nikola Ciprich
2011-01-09 14:13                             ` Avi Kivity
2011-01-09 14:13                           ` Avi Kivity
2011-01-09 14:27                             ` Nikola Ciprich
2011-01-09 14:36                               ` Avi Kivity
2011-01-09 15:15                                 ` Nikola Ciprich
2011-01-09 20:10                                   ` Nikola Ciprich
2011-01-10  9:23                                     ` Avi Kivity

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=4D259729.2050403@redhat.com \
    --to=avi@redhat.com \
    --cc=berrange@redhat.com \
    --cc=extmaillist@linuxbox.cz \
    --cc=kvm@vger.kernel.org \
    --cc=nikola.ciprich@linuxbox.cz \
    /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.