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

Message-ID: <4ADAD561.9060901@goop.org>
Date:	Sun, 18 Oct 2009 17:44:17 +0900
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Avi Kivity <avi@...hat.com>
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/18/09 17:23, Avi Kivity wrote:
>> On the other hand, there's nothing to stop us from moving to multiple
>> pages in future (either to support NUMA placement, or just more than 64
>> cpus).
>>    
>
> I'm already allocating multiple pages, so we'd just need to adjust the
> fixmap.

Are you changing pvclock_init_vsyscall() to allocate more pages?  More
fixmap slots should be no problem.

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