linux-kernel - Re: [V6][PATCH 4/6] x86, nmi: add in logic to handle multiple events and unknown NMIs

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: <4E886F77.9000909@redhat.com>
Date:	Sun, 02 Oct 2011 16:04:39 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Don Zickus <dzickus@...hat.com>,
	Robert Richter <robert.richter@....com>,
	"x86@...nel.org" <x86@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	"ying.huang@...el.com" <ying.huang@...el.com>,
	LKML <linux-kernel@...r.kernel.org>,
	"paulmck@...ux.vnet.ibm.com" <paulmck@...ux.vnet.ibm.com>,
	"jeremy@...p.org" <jeremy@...p.org>
Subject: Re: [V6][PATCH 4/6] x86, nmi:  add in logic to handle multiple events
 and unknown NMIs

On 10/02/2011 03:48 PM, Andi Kleen wrote:
> >  Second, I wanted to use NMIs as a way of waking up a vcpu sleeping with
> >  interrupts disabled (in the context of Jeremy's paravirt spinlock
> >  patches).  Looks like we'll have to use paravirtualization for that.
>
> Just use a mode of perf that doesn't use NMIs.
> Interrupt off profiling is rarely needed if at all on modern kernels.

I tend to agree.   But that's not my call.

(note 'perf kvm' will need adjustment if we make that change - likely 
need to capture the interrupt during vmexit and dispatch it manually; 
not sure if it's workable for svm at all)

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