From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: performance tuning, problem with paravirtualized clock
Date: Mon, 7 Apr 2008 22:47:47 +0200 (CEST) [thread overview]
Message-ID: <alpine.LRH.1.10.0804071747550.27793@linuxbox.linuxbox.cz> (raw)
In-Reply-To: <20080407154127.GA10669@dmt>
Hi Marcelo!
>> Host machine: 2x quad core XEON E5420 @ 2.50GHz, 4GB RAM, 2.6.24 + kvm-64
>> guest configuration: all 8 cores available, 2GB RAM, 2.6.24 or latest GIT
>> + kvm-64
> Can you please provide more details on this? Which kernel version are
> you running on the host?
As I wrote, I use 2.6.24 for the host (+ kvm-65 at the moment), and I'm
trying both 2.6.24 and git for the guest.
>
> Please try -git (there was a lock inversion problem in the KVM clock
> which could cause lock ups).
Unfortunately the problem persists with today's git with kvm-65 patch
applied.
> You might want to pin each guest VCPU to a physical host CPU and check
> if that makes a difference.
It seems that processes are divided on cores quite well, but I'll try
pinning them explicitly to be sure...
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
prev parent reply other threads:[~2008-04-07 20:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 19:56 performance tuning, problem with paravirtualized clock Nikola Ciprich
2008-04-06 20:38 ` Anthony Liguori
2008-04-06 21:57 ` Nikola Ciprich
2008-04-06 22:08 ` Anthony Liguori
2008-04-06 22:24 ` Nikola Ciprich
2008-04-06 22:33 ` Anthony Liguori
2008-04-06 20:49 ` Dor Laor
2008-04-06 22:25 ` Nikola Ciprich
2008-04-07 4:14 ` Avi Kivity
2008-04-07 15:41 ` Marcelo Tosatti
2008-04-07 20:47 ` Nikola Ciprich [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=alpine.LRH.1.10.0804071747550.27793@linuxbox.linuxbox.cz \
--to=extmaillist@linuxbox.cz \
--cc=kvm-devel@lists.sourceforge.net \
--cc=mtosatti@redhat.com \
/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