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=-7.3 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,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 3D50FC433FE for ; Wed, 9 Dec 2020 23:18:10 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (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 ED06A238EB for ; Wed, 9 Dec 2020 23:18:09 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org ED06A238EB Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=xen.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from list by lists.xenproject.org with outflank-mailman.48847.86417 (Exim 4.92) (envelope-from ) id 1kn8ie-0008CA-QH; Wed, 09 Dec 2020 23:18:00 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 48847.86417; Wed, 09 Dec 2020 23:18:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1kn8ie-0008C2-Mr; Wed, 09 Dec 2020 23:18:00 +0000 Received: by outflank-mailman (input) for mailman id 48847; Wed, 09 Dec 2020 23:17:59 +0000 Received: from mail.xenproject.org ([104.130.215.37]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1kn8ic-0008Bw-W3 for xen-devel@lists.xenproject.org; Wed, 09 Dec 2020 23:17:58 +0000 Received: from xenbits.xenproject.org ([104.239.192.120]) by mail.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1kn8ib-0004qF-Va; Wed, 09 Dec 2020 23:17:57 +0000 Received: from [54.239.6.185] (helo=a483e7b01a66.ant.amazon.com) by xenbits.xenproject.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kn8ib-00018l-Pr; Wed, 09 Dec 2020 23:17:57 +0000 X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=xen.org; s=20200302mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:Cc:To:Subject; bh=ZSTBGZi7SQDw33eWOlRaH5mwEbg7Txz4jY2GfV0b96U=; b=co3/Kxtv9nG0WP5KTT9FhS54qe r+Ry1wwTmna2mKGbsldw30ZgW8Tv8su2BVWGt7pCB1w+l+Gd3ASvMhn9Kd6mg5hGrQFhjPUxz0APG mahAoVrBdJBD3WuRyQtMvhbz0+MEI9Mff+lGKxawiNsrtPadF5TZxNVzzaQlNt7rY5m8=; Subject: Re: [PATCH v3 7/7] xen/arm: Activate TID3 in HCR_EL2 To: Bertrand Marquis , xen-devel@lists.xenproject.org Cc: Stefano Stabellini , Volodymyr Babchuk References: <956cf336ffce24f0cabfc7a98ae855bc71d5f028.1607524536.git.bertrand.marquis@arm.com> From: Julien Grall Message-ID: <6e81e7ff-9cfc-aaec-e1fc-336dec06dd6d@xen.org> Date: Wed, 9 Dec 2020 23:17:56 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.5.1 MIME-Version: 1.0 In-Reply-To: <956cf336ffce24f0cabfc7a98ae855bc71d5f028.1607524536.git.bertrand.marquis@arm.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Hi Bertrand, On 09/12/2020 16:31, Bertrand Marquis wrote: > Activate TID3 bit in HSR register when starting a guest. s/HSR/HCR/ > This will trap all coprecessor ID registers so that we can give to guest > values corresponding to what they can actually use and mask some > features to guests even though they would be supported by the underlying > hardware (like SVE or MPAM). So this will make sure the guest will not be able to identify the feature. Did you check that the features are effectively not accessible by the guest? IOW it should trap. Cheers, -- Julien Grall