linux-kernel - Re: [PATCH 5/5] fix kvm's use of _

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: <50FD901C.8000002@linux.vnet.ibm.com>
Date:	Mon, 21 Jan 2013 10:59:40 -0800
From:	Dave Hansen <dave@...ux.vnet.ibm.com>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	Gleb Natapov <gleb@...hat.com>, x86@...nel.org,
	Marcelo Tosatti <mtosatti@...hat.com>,
	Rik van Riel <riel@...hat.com>
Subject: Re: [PATCH 5/5] fix kvm's use of __pa() on percpu areas

On 01/21/2013 10:38 AM, H. Peter Anvin wrote:
> Final question: are any of these done in frequent paths?  (I believe no, but...)

Nope.  All of the places that it gets used here are in
initialization-time paths.  The two we have here are when kvm and the
host are setting up a new vcpu and when the kvmclock clocksource is
being registered.  A CPU getting hotplugged is the only thing that might
even have these get called more than at boot.

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