From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 95774C433E6 for ; Mon, 8 Feb 2021 18:33:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 5247264E6D for ; Mon, 8 Feb 2021 18:33:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234316AbhBHSca (ORCPT ); Mon, 8 Feb 2021 13:32:30 -0500 Received: from mga05.intel.com ([192.55.52.43]:38419 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233828AbhBHQMK (ORCPT ); Mon, 8 Feb 2021 11:12:10 -0500 IronPort-SDR: 1mcaaaruglw7EEKyvzwJPbYXlN+2DT+lDwxa7T46xBAkRrXsPkLTKE8YFbMjiCZpqnR2TS7b25 Fn0b8gBbFCZw== X-IronPort-AV: E=McAfee;i="6000,8403,9889"; a="266569109" X-IronPort-AV: E=Sophos;i="5.81,162,1610438400"; d="scan'208";a="266569109" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Feb 2021 08:11:25 -0800 IronPort-SDR: XzJrWnxkAtcJHpNU5MS+kFte3K3H7htIwsiJvSQG1O75or1u1ubIRfbIrJWztHDJgL9Rho10gm r57SaWrsCM8A== X-IronPort-AV: E=Sophos;i="5.81,162,1610438400"; d="scan'208";a="395525574" Received: from yyu32-mobl1.amr.corp.intel.com (HELO [10.251.11.33]) ([10.251.11.33]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Feb 2021 08:11:24 -0800 Subject: Re: [GIT PULL] x86/urgent for v5.11-rc7 To: Dave Hansen , Alexei Starovoitov Cc: Borislav Petkov , Linus Torvalds , Steven Rostedt , x86-ml , lkml References: <20210207104022.GA32127@zn.tnic> <20210207175814.GF32127@zn.tnic> <661b9809-2c6a-5fc8-163b-a159b84c9ab8@intel.com> <0ea22b5e-9bf5-37d5-0020-03ad2bd48923@intel.com> From: "Yu, Yu-cheng" Message-ID: Date: Mon, 8 Feb 2021 08:11:23 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 MIME-Version: 1.0 In-Reply-To: <0ea22b5e-9bf5-37d5-0020-03ad2bd48923@intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/7/2021 2:35 PM, Dave Hansen wrote: > 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? > I have some kernel-mode enabling patches that I will soon send internally for comments. My estimate is probably before the summer, I can send those to the mailing list. -- Yu-cheng