Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: "George-Cristian Bîrzan" <gc@birzan.org>, kvm@vger.kernel.org
Subject: Re: Performance issue
Date: Tue, 27 Nov 2012 22:38:38 +0200	[thread overview]
Message-ID: <201211272238.38614.vrozenfe@redhat.com> (raw)
In-Reply-To: <20121127145447.GJ12969@redhat.com>

On Tuesday, November 27, 2012 04:54:47 PM Gleb Natapov wrote:
> On Tue, Nov 27, 2012 at 02:29:20PM +0200, George-Cristian Bîrzan wrote:
> > On Tue, Nov 27, 2012 at 2:20 PM, Gleb Natapov <gleb@redhat.com> wrote:
> > > On Mon, Nov 26, 2012 at 09:31:19PM +0200, George-Cristian Bîrzan wrote:
> > >> On Sun, Nov 25, 2012 at 6:17 PM, George-Cristian Bîrzan <gc@birzan.org> 
wrote:
> > >> > On Sun, Nov 25, 2012 at 5:19 PM, Gleb Natapov <gleb@redhat.com> 
wrote:
> > >> >> What Windows is this? Can you try changing "-cpu host" to "-cpu
> > >> >> host,+hv_relaxed"?
> > >> > 
> > >> > This is on Windows Server 2008 R2 (sorry, forgot to mention that I
> > >> > guess), and I can try it tomorrow (US time), as getting a stream my
> > >> > way depends on complicated stuff. I will though, and let you know
> > >> > how it goes.
> > >> 
> > >> I changed that, no difference.
> > > 
> > > Heh, I forgot that the part that should make difference is not yet
> > > upstream :(
> > 
> > We can try recompiling kvm/qemu with some patches, if that'd help. At
> > this point, anything is on the table except changing Windows and the
> > hardware :-)
> 
> Vadim do you have Hyper-v reference timer patches for KVM to try?
I have some code which do both reference time and invariant TSC but it
will not work after migration. I will send it later today.
Vadim.
> 
> > Also, it might be that the software doing the actual work is not well
> > written, but even so...
> > 
> > --
> > George-Cristian Bîrzan
> 
> --
> 			Gleb.

  reply	other threads:[~2012-11-27 20:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22 19:17 Performance issue George-Cristian Bîrzan
2012-11-23  7:26 ` Stefan Hajnoczi
     [not found]   ` <CAMxNYabWpHqmNN7mCY9mwVJjoTj4jwS_js+cZcxQVnJsTdwfBg@mail.gmail.com>
2012-11-23 14:02     ` Fwd: " George-Cristian Bîrzan
2012-11-25 15:19 ` Gleb Natapov
2012-11-25 16:17   ` George-Cristian Bîrzan
2012-11-26 19:31     ` George-Cristian Bîrzan
2012-11-27 12:20       ` Gleb Natapov
2012-11-27 12:29         ` George-Cristian Bîrzan
2012-11-27 14:54           ` Gleb Natapov
2012-11-27 20:38             ` Vadim Rozenfeld [this message]
2012-11-27 21:13               ` George-Cristian Bîrzan
2012-11-28 11:39                 ` Vadim Rozenfeld
2012-11-28 19:09                   ` George-Cristian Bîrzan
2012-11-29 11:56                     ` Vadim Rozenfeld
2012-11-29 13:45                       ` George-Cristian Bîrzan
2012-11-29 13:56                         ` Gleb Natapov
2012-11-29 20:34                           ` Vadim Rozenfeld
2012-11-28 19:18                   ` George-Cristian Bîrzan
2012-11-28 19:56                     ` Gleb Natapov
2012-11-28 20:01                       ` George-Cristian Bîrzan
2012-11-28 20:12                         ` Gleb Natapov

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=201211272238.38614.vrozenfe@redhat.com \
    --to=vrozenfe@redhat.com \
    --cc=gc@birzan.org \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.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