linux-kernel - Re: [tip:perfcounters/core] perf_counter: x86: Fix call-chain support to use NMI-safe methods

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: <4A375D6B.3000105@redhat.com>
Date:	Tue, 16 Jun 2009 11:52:59 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	"H. Peter Anvin" <hpa@...or.com>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	mingo@...hat.com, paulus@...ba.org, acme@...hat.com,
	linux-kernel@...r.kernel.org, a.p.zijlstra@...llo.nl,
	penberg@...helsinki.fi, vegard.nossum@...il.com, efault@....de,
	jeremy@...p.org, npiggin@...e.de, tglx@...utronix.de,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perfcounters/core] perf_counter: x86: Fix call-chain	support
 to use NMI-safe methods

On 06/16/2009 11:36 AM, Ingo Molnar wrote:
>
>>> I can try to find out internally what Intel's position on writing
>>> %cr2 is, but it'll take a while; however, KVM should be able to
>>> tell you if any random OS uses %cr2 writes (as should a static
>>> disassembly of their kernel.)
>>>        
>> Linux is one such OS.  When acting as a hypervisor it writes cr2
>> to present its guests with their expected environment (any
>> hypervisor that uses virtualization extensions will of course need
>> to do this).
>>      
>
> Ah, it does save/restore it in svm_vcpu_run. VMX can do this via its
> context structure (without explicit CR manipulations in host space),
> right?
>    

It's the other way around.  svm switches the guest cr2 in hardware 
(through svm->vmcb->save.cr2).  The code you're referring to saves and 
restores the host cr2, which is completely unnecessary.  I'm currently 
in the middle of dropping it :)

vmx has no hardware support for switching cr2, so vmx_vcpu_run() 
switches it using mov cr2.  Given that it's pretty expensive, I've 
switched it to write-if-changed, which dropped 70 cycles from the vmexit 
latency.

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