From: Andrea Arcangeli <andrea@qumranet.com>
To: Cam Macdonell <cam@cs.ualberta.ca>
Cc: kvm@vger.kernel.org
Subject: Re: Benchmarking on CentOS 5
Date: Wed, 28 May 2008 20:33:52 +0200 [thread overview]
Message-ID: <20080528183352.GE8086@duo.random> (raw)
In-Reply-To: <483D9AE5.6040509@cs.ualberta.ca>
On Wed, May 28, 2008 at 11:48:21AM -0600, Cam Macdonell wrote:
>
> Hi,
>
> I wanted to some benchmarking on a CentOS 5 host. However, the warning in
> dmesg about preempt notifiers indicates I shouldn't benchmark. Is there a
> workaround (aside from updating the kernel) that handles the issue?
The problem is that the preempt notifier emulation through hardware
breakpoints is worse at optimizing lightweight vm exists than the real
preempt notifiers supported by recent kernels. If you benchmark
without upgrading the kernel, it has to be clear it is running slower
than it would on a recent optimized host kernel. If you decide to
upgrade and compile the host kernel yourself, you need to configure it
with CONFIG_KVM=m to be sure the preempt notifiers are enabled in the
host kernel and in turn the printk will go away.
Thanks!
next prev parent reply other threads:[~2008-05-28 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 17:48 Benchmarking on CentOS 5 Cam Macdonell
2008-05-28 18:33 ` Andrea Arcangeli [this message]
2008-05-28 20:27 ` Farkas Levente
2008-05-29 9:23 ` Andrea Arcangeli
2008-05-29 10:13 ` Farkas Levente
[not found] ` <483F75CC.9010303@cisco.com>
[not found] ` <ac75d95a0805300601x4e8b7400sf03280c80813b09e@mail.gmail.com>
[not found] ` <48400371.3060208@cisco.com>
2008-05-30 17:30 ` Farkas Levente
2008-06-01 14:32 ` Andrea Arcangeli
2008-06-02 9:05 ` Amit Shah
2008-06-02 15:56 ` Dor Laor
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=20080528183352.GE8086@duo.random \
--to=andrea@qumranet.com \
--cc=cam@cs.ualberta.ca \
--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