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=-3.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 978E9C5519F for ; Tue, 17 Nov 2020 11:11:47 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 1CCD2207D3 for ; Tue, 17 Nov 2020 11:11:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="BTh+JF7V" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 1CCD2207D3 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=arm.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=eBiDKGKfLh9hW/EW+R/rylFtRhq3fLKtLZ6OKpOfWhE=; b=BTh+JF7V2GGzkN00Bp16ldcvU /HC4guS3DzaEYfZWUebzgsgHth6AwfI02tcHEfkWyCtCg6mqZVlpjDqpsqMkGFiDCQMP5/DBULQD+ E9tlUEYYqJaL0jcw5fARrOXHSUK8TqrQYqaFwmPpHhzhsQ5X4GrUpUZVkhLrH+VP4EkmpS5IRohq7 UGu4jvjMLQxCAMolKO77h5cLNj/fg8bFQOgiKxzt+r3KnkNDd0XyLhnF330H3tJd0ktSwMEjc2Z20 i++NFTHY7if5wRz+WSQwEkR5rLSx7c3HOzztan67xumhJvRbBjjJfo9uwjYMnfa0ErU0NsblU0Bdu BWoJNQ5cg==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1keytN-0003VX-9s; Tue, 17 Nov 2020 11:11:21 +0000 Received: from mail.kernel.org ([198.145.29.99]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1keysq-0003N2-WC for linux-arm-kernel@lists.infradead.org; Tue, 17 Nov 2020 11:11:17 +0000 Received: from trantor (unknown [2.26.170.190]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id AF64A207BC; Tue, 17 Nov 2020 11:10:46 +0000 (UTC) Date: Tue, 17 Nov 2020 11:10:44 +0000 From: Catalin Marinas To: Mark Rutland Subject: Re: [PATCHv4 14/17] arm64: uaccess: remove set_fs() Message-ID: References: <20201113124937.20574-1-mark.rutland@arm.com> <20201113124937.20574-15-mark.rutland@arm.com> <20201117104454.GA73209@C02TD0UTHF1T.local> <20201117105740.GB73209@C02TD0UTHF1T.local> <20201117110758.GC73209@C02TD0UTHF1T.local> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20201117110758.GC73209@C02TD0UTHF1T.local> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20201117_061049_165778_322188FB X-CRM114-Status: GOOD ( 10.87 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: james.morse@arm.com, will@kernel.org, hch@lst.de, linux-arm-kernel@lists.infradead.org, robin.murphy@arm.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Nov 17, 2020 at 11:07:58AM +0000, Mark Rutland wrote: > On Tue, Nov 17, 2020 at 11:02:20AM +0000, Catalin Marinas wrote: > > Could we apply the same logic to SDEI+PAN? > > I don't think we can; existing TF-A FW will clear PAN (since it > generates the new PSTATE from scratch), so we need to set PAN explicitly > to support that. Ah, you are right, we need PAN set (and UAO clear). -- Catalin _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel