From: Dor Laor <dor.laor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Cam Macdonell <cam-edFDblaTWIyXbbII50Afww@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Benchmarking warning
Date: Sat, 26 Jan 2008 01:42:28 +0200 [thread overview]
Message-ID: <1201304548.2944.11.camel@localhost.localdomain> (raw)
In-Reply-To: <479A60B3.9040200-edFDblaTWIyXbbII50Afww@public.gmane.org>
On Fri, 2008-01-25 at 15:20 -0700, Cam Macdonell wrote:
> Hi,
>
> I get the following warning in the kernel messages:
>
> kvm: emulating preempt notifiers; do not benchmark on this machine
>
> Is this an accurate warning, should the machine not be used for
It's accurate.
> benchmarking KVM? or does it mean don't benchmark other applications on
> the host?
>
It's when running kvm (it traps every process scheduling).
On newer hosts (2.6.23 >=) the preempt notifiers are integrated and
there is no need tapping the scheduler.
> Thanks,
> Cam
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2008-01-25 23:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 22:20 Benchmarking warning Cam Macdonell
[not found] ` <479A60B3.9040200-edFDblaTWIyXbbII50Afww@public.gmane.org>
2008-01-25 23:42 ` Dor Laor [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=1201304548.2944.11.camel@localhost.localdomain \
--to=dor.laor-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=cam-edFDblaTWIyXbbII50Afww@public.gmane.org \
--cc=dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 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.