From: Dave Hansen <dave.hansen@intel.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Borislav Petkov <bp@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>, x86-ml <x86@kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
"Yu, Yu-cheng" <yu-cheng.yu@intel.com>
Subject: Re: [GIT PULL] x86/urgent for v5.11-rc7
Date: Sun, 7 Feb 2021 14:35:54 -0800 [thread overview]
Message-ID: <0ea22b5e-9bf5-37d5-0020-03ad2bd48923@intel.com> (raw)
In-Reply-To: <CAADnVQ+Sqna6X2a3MKaBv7xmdCcj-aD=prp8OggTTwCjoVN_0A@mail.gmail.com>
On 2/7/21 12:44 PM, Alexei Starovoitov wrote:
>>> It probably is an item on some Intel manager's to-enable list. So far,
>>> the CET enablement concentrates only on userspace but dhansen might know
>>> more about future plans. CCed.
>> It's definitely on our radar to look at after CET userspace.
> What is the desired timeline to enable CET in the kernel ?
> I think for bpf and tracing it will be mostly straightforward to deal
> with extra endbr64 insn in front of the fentry nop.
> Just trying to figure when this work needs to be done.
Yu-cheng? Any idea when you're going to start hacking on the in-kernel
IBT bits?
next prev parent reply other threads:[~2021-02-07 22:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 10:40 [GIT PULL] x86/urgent for v5.11-rc7 Borislav Petkov
2021-02-07 17:49 ` Linus Torvalds
2021-02-07 17:58 ` Borislav Petkov
2021-02-07 18:15 ` Linus Torvalds
2021-02-07 18:32 ` Dave Hansen
2021-02-07 18:40 ` Linus Torvalds
2021-02-07 22:45 ` Josh Poimboeuf
2021-02-08 15:02 ` Steven Rostedt
2021-02-08 15:33 ` Josh Poimboeuf
2021-02-08 15:47 ` Peter Zijlstra
2021-02-08 16:15 ` Steven Rostedt
2021-02-09 8:32 ` Miroslav Benes
2021-02-09 14:49 ` Steven Rostedt
2021-02-09 15:16 ` Miroslav Benes
2021-02-09 16:45 ` Alexei Starovoitov
2021-02-09 16:55 ` Andy Lutomirski
2021-02-09 18:09 ` Linus Torvalds
2021-02-09 18:26 ` Andy Lutomirski
2021-02-09 18:39 ` Linus Torvalds
2021-02-07 18:19 ` Dave Hansen
2021-02-07 18:31 ` Andy Lutomirski
2021-02-08 10:33 ` Peter Zijlstra
2021-02-07 20:44 ` Alexei Starovoitov
2021-02-07 22:35 ` Dave Hansen [this message]
2021-02-08 16:11 ` Yu, Yu-cheng
2021-02-07 18:29 ` pr-tracker-bot
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=0ea22b5e-9bf5-37d5-0020-03ad2bd48923@intel.com \
--to=dave.hansen@intel.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=yu-cheng.yu@intel.com \
/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