Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 50AECC27C76 for ; Wed, 25 Jan 2023 17:27:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235296AbjAYR1W (ORCPT ); Wed, 25 Jan 2023 12:27:22 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51088 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229612AbjAYR1U (ORCPT ); Wed, 25 Jan 2023 12:27:20 -0500 Received: from mail.zytor.com (unknown [IPv6:2607:7c80:54:3::138]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D348E30E9; Wed, 25 Jan 2023 09:27:18 -0800 (PST) Received: from [127.0.0.1] ([73.223.250.219]) (authenticated bits=0) by mail.zytor.com (8.17.1/8.17.1) with ESMTPSA id 30PHOh0f3191260 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Wed, 25 Jan 2023 09:24:43 -0800 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.zytor.com 30PHOh0f3191260 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zytor.com; s=2023010601; t=1674667484; bh=E6ZzjSvSbOY36CL4Ti5rEQx63MkTAMDPF+DyyM4GwZs=; h=Date:From:To:CC:Subject:In-Reply-To:References:From; b=dxTDz57hBamdDcZbJiBjHk5SCcxYmmC7kpsvv/b/0vkYBstNrKJpJA3MmZhEDaDgo +qP2uCpDjkKh3ExV/Q7SdTmsGhmDvzhUV4JEQbxLT3EkZZ00iNFTy/dXAeyWPkO/YL ax85Silr+iqPkWqJD14N06T9qv3BkUUpQTrbhT/4jr13HNlIB1rWh7iJrN2xEzgjGs 3WWP0+QTsUYNwjniu1eRAF636DHVomElYfMzWJxmq3LaEOtvT7WC4LulLbzzWoAQn2 usAGv5mrlp21A7URRoO+k7hLqWQztYTDbkbSzVPHg1OWHsgeODhKBptRJYWvrgncpK DDNIotQd3xbUw== Date: Wed, 25 Jan 2023 09:24:40 -0800 From: "H. Peter Anvin" To: "Li, Xin3" , Ammar Faizi CC: "Hansen, Dave" , Dave Hansen , Thomas Gleixner , "andrew.cooper3@citrix.com" , Brian Gerst , Ingo Molnar , Borislav Petkov , Peter Zijlstra , Shuah Khan , Ingo Molnar , "Lutomirski, Andy" , x86 Mailing List , "Kirill A. Shutemov" , Linux Kselftest Mailing List , Linux Kernel Mailing List Subject: =?US-ASCII?Q?RE=3A_=5BRFC_PATCH_v5_0/2=5D_sysret=5Frip_up?= =?US-ASCII?Q?date_for_the_Intel_FRED_architecture?= User-Agent: K-9 Mail for Android In-Reply-To: References: <6cd0db14-c9e2-3598-fd10-4b473d78c373@citrix.com> <5ecc383c-621b-57d9-7f6d-d63496fca3b3@zytor.com> <20230124022729.596997-1-ammarfaizi2@gnuweeb.org> <20230124022729.596997-3-ammarfaizi2@gnuweeb.org> <20230125034958.734527-1-ammarfaizi2@gnuweeb.org> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On January 25, 2023 9:07:18 AM PST, "Li, Xin3" wrot= e: >> > This version passes on FRED, thanks a lot for quickly fixing it=2E >>=20 >> Great! >>=20 >> Can you pick these two patches and include it in the next version of >> "x86: enable FRED for x86-64" RFC patchset? > >Would it be better to get this patch set merged first? > >Otherwise surely I will include it in the FRED patch set=2E > > Xin > >=20 > If the maintainers are ok with it, it would be better to merge it sooner: = once we have agreed on the semantics, which I believe we have, we should be= testing those semantics and nothing else=2E