From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Marcelo Tosatti <marcelo-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>
Cc: kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH] report revision 3 of the ACPI/SMBus PIIX4 controller
Date: Sun, 13 Jan 2008 12:25:18 +0200 [thread overview]
Message-ID: <4789E70E.7040802@qumranet.com> (raw)
In-Reply-To: <20080111212655.GA28753@dmt>
Marcelo Tosatti wrote:
> The PIIX4 ACPI controller prior to revision 0x3 contains a bug where
> reading of the timer port is unreliable, so the kernel reads it three
> times for consistency check.
>
> QEMU does not suffer from that problem :)
>
> The datasheet for PIIX4, PIIX4E, and PIIX4M is the same. I failed to
> find any indication that the revision increase could affect anything
> other than the PMTimer port read.
>
> This reduces idle guest CPU consumption from 14% to 8% on 4-way KVM
> guest.
>
>
Applied (to kvm's qemu), thanks.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
next prev parent reply other threads:[~2008-01-13 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 21:26 [PATCH] report revision 3 of the ACPI/SMBus PIIX4 controller Marcelo Tosatti
2008-01-13 10:25 ` Avi Kivity [this message]
2008-01-13 11:19 ` Anders
[not found] ` <87ve5yynuv.fsf-MhEMtRviUwpApvB0Y80ENH9LOBIZ5rWg@public.gmane.org>
2008-01-13 14:22 ` Marcelo Tosatti
2008-01-13 15:49 ` Anders
[not found] ` <878x2tzpx4.fsf-MhEMtRviUwpApvB0Y80ENH9LOBIZ5rWg@public.gmane.org>
2008-01-14 13:24 ` Marcelo Tosatti
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=4789E70E.7040802@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=marcelo-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=qemu-devel-qX2TKyscuCcdnm+yROfE0A@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox