linux-kernel - [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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 22 Jan 2015 16:29:09 -0800
From:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>
To:	david.vrabel@...rix.com, konrad.wilk@...cle.com,
	boris.ostrovsky@...cle.com, xen-devel@...ts.xenproject.org
Cc:	linux-kernel@...r.kernel.org, x86@...nel.org, kvm@...r.kernel.org,
	paulmck@...ux.vnet.ibm.com, rostedt@...dmis.org,
	"Luis R. Rodriguez" <mcgrof@...e.com>
Subject: [RFC v4 0/2] x86/xen: add xen hypercall preemption

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?

Luis R. Rodriguez (2):
  x86/xen: add xen_is_preemptible_hypercall()
  x86/xen: allow privcmd hypercalls to be preempted

 arch/arm/include/asm/xen/hypercall.h |  5 +++++
 arch/x86/include/asm/xen/hypercall.h | 20 ++++++++++++++++++++
 arch/x86/kernel/entry_32.S           |  2 ++
 arch/x86/kernel/entry_64.S           |  2 ++
 arch/x86/xen/enlighten.c             |  7 +++++++
 arch/x86/xen/xen-head.S              | 18 +++++++++++++++++-
 drivers/xen/events/events_base.c     | 23 +++++++++++++++++++++++
 include/trace/events/xen.h           |  9 +++++++++
 include/xen/events.h                 |  1 +
 9 files changed, 86 insertions(+), 1 deletion(-)

-- 
2.1.1

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