linux-kernel - Re: [patch 0/3] kvm tool: Serial emulation overhaul

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 13 Dec 2011 16:58:24 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Thomas Gleixner <tglx@...utronix.de>
CC:	Ingo Molnar <mingo@...e.hu>, Pekka Enberg <penberg@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Sasha Levin <levinsasha928@...il.com>
Subject: Re: [patch 0/3] kvm tool: Serial emulation overhaul

On 12/13/2011 04:51 PM, Thomas Gleixner wrote:
> > > The whole APIC timer calibration and the back and forth
> > > conversion is definitely nothing which falls into the category of
> > > smart.
> > 
> > APIC timer calibration is silly but it hasn't proven to be a real-world
> > problem.
>
> Well, that depends on the world. 

What I mean by that, is that I haven't seen any bug reports in this area
apart from some issue with wiring the PIT/PIC/APIC correctly which were
resolved long ago.

> The issue with that calibration is
> that it can be off and for a certain category of application it
> matters. Definitely not for the usual virt workload stuff. But saving
> cycles for highres/nohz enabled guests would be nice. Maybe I have a
> go when I find a some time.

Just dropping the calibration an replacing it with a pre-calibrated
value should be simple, if there is a workload that could benefit.

-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/