From: Ingo Molnar <mingo@kernel.org>
To: Andy Lutomirski <luto@kernel.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Borislav Petkov <bp@alien8.de>, Oleg Nesterov <oleg@redhat.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Brian Gerst <brgerst@gmail.com>
Subject: Re: [PATCH 00/10] x86: Various SYSENTER/SYSEXIT/#DB fixes and cleanups
Date: Sun, 6 Mar 2016 09:22:11 +0100 [thread overview]
Message-ID: <20160306082211.GA12352@gmail.com> (raw)
In-Reply-To: <cover.1457243356.git.luto@kernel.org>
* Andy Lutomirski <luto@kernel.org> wrote:
> This series applies to the result of merging tip:x86/asm and
> tip:x86/urgent. I've been testing on a somewhat bastardized base,
> because tip currently doesn't work on my laptop in 32-bit mode. (That
> bug is fixed in Linus' tree.)
Hm, which fix is that?
Generally, tip:master closely tracks Linus's latest (so it should work as-is), but
individual sub-trees are only updated when necessary - but a refresh can be done
anytime if requested.
Thanks,
Ingo
next prev parent reply other threads:[~2016-03-06 8:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 5:52 [PATCH 00/10] x86: Various SYSENTER/SYSEXIT/#DB fixes and cleanups Andy Lutomirski
2016-03-06 5:52 ` [PATCH v2 01/10] selftests/x86: In syscall_nt, test NT|TF as well Andy Lutomirski
2016-03-06 5:52 ` [PATCH v2 02/10] x86/entry/compat: In SYSENTER, sink AC clearing below the existing FLAGS test Andy Lutomirski
2016-03-06 5:52 ` [PATCH v2 03/10] x86/entry/32: Filter NT and speed up AC filtering in SYSENTER Andy Lutomirski
2016-03-06 5:52 ` [PATCH v2 04/10] x86/entry/32: Restore FLAGS on SYSEXIT Andy Lutomirski
2016-03-06 5:52 ` [PATCH v2 05/10] x86/traps: Clear TIF_BLOCKSTEP on all debug exceptions Andy Lutomirski
2016-03-06 5:52 ` [PATCH v2 06/10] x86/traps: Clear DR6 early in do_debug and improve the comment Andy Lutomirski
2016-03-06 5:52 ` [PATCH v2 07/10] x86/entry: Vastly simplify SYSENTER TF handling Andy Lutomirski
2016-03-06 16:55 ` Borislav Petkov
2016-03-06 17:30 ` Brian Gerst
2016-03-06 17:36 ` Andy Lutomirski
2016-03-06 18:01 ` Borislav Petkov
2016-03-06 18:20 ` Andrew Cooper
2016-03-07 17:17 ` Brian Gerst
2016-03-07 18:03 ` Andy Lutomirski
2016-03-07 18:41 ` Brian Gerst
2016-03-07 18:46 ` Andy Lutomirski
2016-03-06 5:52 ` [PATCH v2 08/10] x86/entry: Only allocate space for SYSENTER_stack if needed Andy Lutomirski
2016-03-06 5:52 ` [PATCH v2 09/10] x86/entry/32: Simplify and fix up the SYSENTER stack #DB/NMI fixup Andy Lutomirski
2016-03-08 6:36 ` Borislav Petkov
2016-03-06 5:52 ` [PATCH v2 10/10] x86/entry/32: Add and check a stack canary for the SYSENTER stack Andy Lutomirski
2016-03-08 6:40 ` Borislav Petkov
2016-03-09 21:22 ` Andy Lutomirski
2016-03-06 8:22 ` Ingo Molnar [this message]
2016-03-06 16:16 ` [PATCH 00/10] x86: Various SYSENTER/SYSEXIT/#DB fixes and cleanups Andy Lutomirski
2016-03-07 8:29 ` Ingo Molnar
2016-03-06 8:31 ` Ingo Molnar
2016-03-06 16:16 ` Andy Lutomirski
-- strict thread matches above, loose matches on Subject: below --
2016-02-29 5:28 Andy Lutomirski
2016-02-29 18:55 ` Andy Lutomirski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160306082211.GA12352@gmail.com \
--to=mingo@kernel.org \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=oleg@redhat.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).