linux-kernel - Re: [GIT PULL RFC] pvclock cleanups and pvclock vsyscall support

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4ADAB8F4.6090502@redhat.com>
Date:	Sun, 18 Oct 2009 15:43:00 +0900
From:	Avi Kivity <avi@...hat.com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
CC:	Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Xen-devel <xen-devel@...ts.xensource.com>,
	kurt.hackel@...cle.com,
	Glauber de Oliveira Costa <gcosta@...hat.com>,
	the arch/x86 maintainers <x86@...nel.org>,
	Chris Mason <chris.mason@...cle.com>
Subject: Re: [GIT PULL RFC] pvclock cleanups and pvclock vsyscall support

On 10/16/2009 04:46 AM, Jeremy Fitzhardinge wrote:
> Care to cook up a patch to implement the kvm bits to make sure it all
> works OK for you?
>    

I've started to do that, but it occurs to me that we're missing out on 
NUMA placement by forcing all clocks to be on the same page. OTOH, if 
the clocks are heavily used, they'll stay in cache, and if not, who cares.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

--
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/