On Sun, Jan 13, 2008 at 04:49:27PM +0100, Anders wrote:
> Marcelo Tosatti <[EMAIL PROTECTED]> writes:
>
> > On Sun, Jan 13, 2008 at 12:19:20PM +0100, Anders wrote:
>
> [...]
>
> >> How do you get that high consumption? What combination of clocks/hz on
> >> host/guest are you using?
> >
> > CONFI
Marcelo Tosatti <[EMAIL PROTECTED]> writes:
> On Sun, Jan 13, 2008 at 12:19:20PM +0100, Anders wrote:
[...]
>> How do you get that high consumption? What combination of clocks/hz on
>> host/guest are you using?
>
> CONFIG_HZ=250
Okay, with nohz=off (in the guest) I also see some higher load. I
On Sun, Jan 13, 2008 at 12:19:20PM +0100, Anders wrote:
> Marcelo Tosatti <[EMAIL PROTECTED]> writes:
>
> > This reduces idle guest CPU consumption from 14% to 8% on 4-way KVM
> > guest.
>
> How do you get that high consumption? What combination of clocks/hz on
> host/guest are you using?
CONFIG
Marcelo Tosatti <[EMAIL PROTECTED]> writes:
> This reduces idle guest CPU consumption from 14% to 8% on 4-way KVM
> guest.
How do you get that high consumption? What combination of clocks/hz on
host/guest are you using?
I am cursious, since my idle KVM process is at less than 1%.
Regards,
Ande
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 s
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 indicati
