linux-kernel - Re: [Xen-devel] [RFC v4 0/2] x86/xen: add xen hypercall preemption

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <54C235AD.5010202@citrix.com>
Date:	Fri, 23 Jan 2015 11:51:09 +0000
From:	David Vrabel <david.vrabel@...rix.com>
To:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>,
	<david.vrabel@...rix.com>, <konrad.wilk@...cle.com>,
	<boris.ostrovsky@...cle.com>, <xen-devel@...ts.xenproject.org>
CC:	<kvm@...r.kernel.org>, "Luis R. Rodriguez" <mcgrof@...e.com>,
	<x86@...nel.org>, <linux-kernel@...r.kernel.org>,
	<rostedt@...dmis.org>, <paulmck@...ux.vnet.ibm.com>
Subject: Re: [Xen-devel] [RFC v4 0/2] x86/xen: add xen hypercall preemption

On 23/01/15 00:29, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@...e.com>
> 
> This v4 addresses some of the cleanups recommended and adds
> tracing option for when we do actually preempt a hypercall.
> I kept the NOKPROBE_SYMBOL() for now but did remove the 'notrace'
> stuff.
> 
> This goes out as RFC still as I have not been able to test 32-bit.
> Can anyone test that or at least confirm that the 32-bit point
> we do the upcall is definitely not on the IRQ stack?

You can omit fixing this for 32-bit guests (provided you note as such in
the commit message).

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