Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: "George-Cristian Bîrzan" <gc@birzan.org>
Cc: Vadim Rozenfeld <vrozenfe@redhat.com>, kvm@vger.kernel.org
Subject: Re: Performance issue
Date: Thu, 29 Nov 2012 15:56:10 +0200	[thread overview]
Message-ID: <20121129135610.GB17318@redhat.com> (raw)
In-Reply-To: <CAMxNYabsXzX93oGcX5BfHqoNV-X=kBbA7DgHaQQyjYy9KR753w@mail.gmail.com>

On Thu, Nov 29, 2012 at 03:45:52PM +0200, George-Cristian Bîrzan wrote:
> On Thu, Nov 29, 2012 at 1:56 PM, Vadim Rozenfeld <vrozenfe@redhat.com> wrote:
> >> I've also added +hv_relaxed since then, but this is the command I'm
> >
> > I would suggest activating relaxed timing for all W2K8R2/Win7 guests.
> 
> Is there any place I can read up on the downsides of this for Linux,
> or is Just Better?
> 
You shouldn't use hyper-v flags for Linux guests. In theory Linux should
just ignore them, in practice there may be bugs that will prevent Linux
from detecting that it runs as a guest and disable optimizations.

> >>>> Other than that, was looking into a profiling trace of the software
> >> running and a lot of time (60%?) is spent calling two functions from
> >> hal.dll, HalpGetPmTimerSleepModePerfCounter when I disable HPET, and
> >> HalpHPETProgramRolloverTimer which do point at something related to
> >> the timers.
> >>
> > It means that hyper-v time stamp source was not activated.
> 
> I recompiled the whole kernel, with your patch, and while I cannot
> check at 70Mbps now, a test stream of 20 seems to do better. Also, now
> I don't see any of those functions, which used to account ~60% of the
> time spent by the program. I'm waiting for the customer to come back
> and start the 'real' stream, but from my tests, time spent in hal.dll
> is now an order of magnitude smaller.
> 
> --
> George-Cristian Bîrzan

--
			Gleb.

  reply	other threads:[~2012-11-29 14:12 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
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 [this message]
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=20121129135610.GB17318@redhat.com \
    --to=gleb@redhat.com \
    --cc=gc@birzan.org \
    --cc=kvm@vger.kernel.org \
    --cc=vrozenfe@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