linux-kernel - Re: [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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <56302D69.8000101@redhat.com>
Date:	Wed, 28 Oct 2015 03:05:29 +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: Re: [PATCH 0/3] context_tracking: streamline code, avoid IRQ
 save/restore



On 28/10/2015 02:39, Paolo Bonzini wrote:
> 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. :)

Heh, Andy said it doesn't. :)

However, we could still merge the first two patches for 4.4 since they
have been tested.  I can even take them myself if I get Acked-by.  The
third one will have to wait for 4.5.

Thanks,

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