linux-kernel - [PATCH 0/3] context_tracking: streamline code, avoid IRQ save/restore

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:	Wed, 28 Oct 2015 02:39:54 +0100
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Cc:	Andy Lutomirski <luto@...nel.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Rik van Riel <riel@...hat.com>,
	Paul McKenney <paulmck@...ux.vnet.ibm.com>
Subject: [PATCH 0/3] context_tracking: streamline code, avoid IRQ save/restore

The first two of these patches were posted last February, the last one
is new.  Rik's old measurements were that it shaved around .3 microseconds
on each iteration of his KVM benchmark.

I guess three days before the start of the merge window is not
the best time to post patches.  However, I brought this series up at
kernel summit yesterday, and Andy's cleanups actually makes it trivial
to apply this to syscall entry.  So here it is, perhaps it's worth it.

Assuming it works, of course, because this is compile-tested only. :)

Paolo

Paolo Bonzini (3):
  context_tracking: remove duplicate enabled check
  context_tracking: avoid irq_save/irq_restore on guest entry and exit
  x86: context_tracking: avoid irq_save/irq_restore on kernel entry and exit

 arch/x86/entry/common.c          |  4 +-
 include/linux/context_tracking.h | 50 +++++++++++++++++--------
 kernel/context_tracking.c        | 80 ++++++++++++++++++++--------------------
 3 files changed, 76 insertions(+), 58 deletions(-)

-- 
2.5.0

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