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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 4D179C352A1 for ; Wed, 7 Dec 2022 14:01:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: Content-Transfer-Encoding:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date:Message-ID:From: References:CC:To:Subject:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=XXblAPLcPg53KEfMkg0fpmN04etRLBmTUJ+4FPnkCM8=; b=insCO0azvso8tPeFyV67lu5i0E nyZxb2sZCt1Cj3t4O0k7tOhMJFPeb+RGko53BYzoPVwbYX8MSDoMAZ46xxSvw1YXPOL7StXd//uCy 46Uaw0ZjJBxJLeuWI2jtR2l3zr2NHWJUi1xVDeGsAAXnoyJqR5PZkVWyW1ii6HtgyWosMSF+xTngk HsEVG/oATPtbqwjzD1RT4VLh0xZkyo+dE3z7UXcDldkEyLc6I81lx+RpbKC4WDURk2Z0sAXb2c3Kk HwL9oXiiwmaElRmbKZgFviG4duyyGoiMgmdOuLhaCfPwltRdqYdrYejZrtEb6X22abgu8fL/N7wGp 8MFcS6Eg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1p2uyN-004NVw-5s; Wed, 07 Dec 2022 14:00:31 +0000 Received: from szxga01-in.huawei.com ([45.249.212.187]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1p2uyH-004NMR-Jq for linux-arm-kernel@lists.infradead.org; Wed, 07 Dec 2022 14:00:27 +0000 Received: from kwepemm600007.china.huawei.com (unknown [172.30.72.53]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4NRzMs4bWqzqSvX; Wed, 7 Dec 2022 21:56:09 +0800 (CST) Received: from [10.174.185.179] (10.174.185.179) by kwepemm600007.china.huawei.com (7.193.23.208) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Wed, 7 Dec 2022 22:00:18 +0800 Subject: Re: [PATCH v14 16/39] arm64/sme: Implement traps and syscall handling for SME To: Mark Brown CC: Catalin Marinas , Will Deacon , Marc Zyngier , Shuah Khan , Shuah Khan , Basant Kumar Dwivedi , Luis Machado , Szabolcs Nagy , , , Alan Hayward , , Salil Akerkar , Luca Salabrino References: <20220419112247.711548-1-broonie@kernel.org> <20220419112247.711548-17-broonie@kernel.org> From: Zenghui Yu Message-ID: Date: Wed, 7 Dec 2022 22:00:17 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 MIME-Version: 1.0 In-Reply-To: <20220419112247.711548-17-broonie@kernel.org> Content-Language: en-US X-Originating-IP: [10.174.185.179] X-ClientProxiedBy: dggems705-chm.china.huawei.com (10.3.19.182) To kwepemm600007.china.huawei.com (7.193.23.208) X-CFilter-Loop: Reflected X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221207_060026_067156_7C08E391 X-CRM114-Status: GOOD ( 21.55 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 2022/4/19 19:22, Mark Brown wrote: > diff --git a/arch/arm64/kernel/syscall.c b/arch/arm64/kernel/syscall.c > index c938603b3ba0..92c69e5ac269 100644 > --- a/arch/arm64/kernel/syscall.c > +++ b/arch/arm64/kernel/syscall.c > @@ -158,11 +158,36 @@ static void el0_svc_common(struct pt_regs *regs, int scno, int sc_nr, > syscall_trace_exit(regs); > } > > -static inline void sve_user_discard(void) > +/* > + * As per the ABI exit SME streaming mode and clear the SVE state not > + * shared with FPSIMD on syscall entry. > + */ > +static inline void fp_user_discard(void) > { > + /* > + * If SME is active then exit streaming mode. If ZA is active > + * then flush the SVE registers but leave userspace access to > + * both SVE and SME enabled, otherwise disable SME for the > + * task and fall through to disabling SVE too. This means It looks a bit confusing to me that in the current implementation, if ZA is *not* active, we don't actually go to disable SME for the task (which IMHO can be disabled as user-space is not actively using it now). > + * that after a syscall we never have any streaming mode > + * register state to track, if this changes the KVM code will > + * need updating. > + */ > + if (system_supports_sme() && test_thread_flag(TIF_SME)) { > + u64 svcr = read_sysreg_s(SYS_SVCR_EL0); > + > + if (svcr & SYS_SVCR_EL0_SM_MASK) > + sme_smstop_sm(); As per the SME syscall ABI | On syscall PSTATE.SM will be cleared and the SVE registers will be | handled as per the standard SVE ABI. and the SVE syscall ABI | On syscall, V0..V31 are preserved (as without SVE). Thus, bits | [127:0] of Z0..Z31 are preserved. All other bits of Z0..Z31, and all | of P0..P15 and FFR become zero on return from a syscall. Can we infer from the documentation that V0-V31 should be preserved on return from a syscall? But with sme_smstop_sm(), all implemented bits of Z0-Z31 are set to zero by hardware. Is this intentional? Please fix me up if I've mis-read things here. > + } > + > if (!system_supports_sve()) > return; > > + /* > + * If SME is not active then disable SVE, the registers will > + * be cleared when userspace next attempts to access them and > + * we do not need to track the SVE register state until then. > + */ > clear_thread_flag(TIF_SVE); > > /* Thanks, Zenghui _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel