Re: [GIT PULL] x86/asm changes for 3.20

[Ingo Molnar]

* Andy Lutomirski <luto@xxxxxxxxxxxxxx> wrote:

> Hi Ingo and Thomas,
> 
> Please consider pulling for x86/asm.  The sysret stuff hasn't been in
> -next, but it's been floating around for a while, and got a reasonably
> favorable reception.
> 
> If you think it's too late for the sysret stuff for 3.20, then please
> pull just "x86, traps: Fix ist_enter from userspace" instead.  It
> fixes a regression.
> 
> Thanks,
> Andy
> 
> The following changes since commit 772a9aca12567badb5b9caf2af249a5991f47ea8:
> 
>   Merge tag 'pr-20150114-x86-entry' of
> git://git.kernel.org/pub/scm/linux/kernel/git/luto/linux into x86/asm
> (2015-01-28 15:33:26 +0100)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git
> tags/pr-20150201-x86-entry
> 
> for you to fetch changes up to 96b6352c12711d5c0bb7157f49c92580248e8146:
> 
>   x86_64, entry: Remove the syscall exit audit and schedule
> optimizations (2015-02-01 04:03:02 -0800)
> 
> ----------------------------------------------------------------
> x86: Entry cleanups and a bugfix for 3.20
> 
> This fixes a bug in the RCU code I added in ist_enter.  It also includes
> the sysret stuff discussed here:
> 
> http://lkml.kernel.org/g/cover.1421453410.git.luto%40amacapital.net
> 
> ----------------------------------------------------------------
> Andy Lutomirski (3):
>       x86, traps: Fix ist_enter from userspace
>       x86_64, entry: Use sysret to return to userspace when possible
>       x86_64, entry: Remove the syscall exit audit and schedule optimizations
> 
>  arch/x86/kernel/entry_64.S | 106 +++++++++++++++++++++++++--------------------
>  arch/x86/kernel/traps.c    |  25 ++++++++---
>  2 files changed, 77 insertions(+), 54 deletions(-)

Pulled, thanks a lot Andy!

I'll give it some extra testing before pushing it out into -tip 
and then towards linux-next.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/