[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 2/3] xen/arm: Advertise workaround 1 if we apply 3
- To: Julien Grall <julien@xxxxxxx>
- From: Bertrand Marquis <Bertrand.Marquis@xxxxxxx>
- Date: Wed, 4 May 2022 07:25:40 +0000
- Accept-language: en-GB, en-US
- Arc-authentication-results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 63.35.35.123) smtp.rcpttodomain=lists.xenproject.org smtp.mailfrom=arm.com; dmarc=pass (p=none sp=none pct=100) action=none header.from=arm.com; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com; arc=pass (0 oda=1 ltdi=1 spf=[1,1,smtp.mailfrom=arm.com] dkim=[1,1,header.d=arm.com] dmarc=[1,1,header.from=arm.com])
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
- Arc-message-signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=4i6aKpT1Q9Wb0tSNFh84E7CqB5bX+55FNc8kTTdRO24=; b=SYpZsjCUtE4g7EkAQCHwpFgaZm5P4IlDoWSnHqSW/nSGGhkAoeHzsM9rWAgWjnpEx/ucHpUMmLDkhoLepHgAzihLhO3j5itjkQgXuXWbAOcoykZEiLRVgzLcsJJ6Gotf6HfLce8GohO6MRt8pPlRI2xZhHIpZaDhtIO0Xf1MDhE2TQ5hUncrzIMVLukhSKE4RNsWyBvPllWBctolHwfSVDEKzLFCa8cJGABf0mZ8Mk22akLCQAhm6KamIpGzzU8IhbqiT8nhsv4g3r2wWN1tBEAN3xvEZTguCURGqpPTHXAk1jYo/E1jUrKJo7iDyRfL/KFymxOuLhSpjJOpjTmsow==
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=4i6aKpT1Q9Wb0tSNFh84E7CqB5bX+55FNc8kTTdRO24=; b=aZQ9JmIkXobb/xQefVbKVgcCbzhTr9QmdDqTTo4paHVnjp/8L4eYBhC6qfMPSwFgtozEYQ0tpZEBMnyky1gRpEImkq7CApYRg7hXv8+rGZW+1DoqN8DH0XmI8JdKS3ktmI6Z0UUnRt0mgoh5ydAOUJjiGbzEn8oiuDnoL3zwzY0UNbwjPK0usXdRktsYzuPXjed5RchfA/xnJs7CLvccNw1no+AOgEOciO7AVFO2uZFUWiiGEMsk9IXAGlwQaXppP2llQDUJEiKRuDLVZkJJqe2yq4DDH2FT9v5EpSxHca4t4xuSg6Una8uHmmbYiIzeM44jAf1NqnchrqtXgdzuqQ==
- Arc-seal: i=2; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=pass; b=L8t9Ij4FFkYD6P9Dcior8pMbleREACfwbTyBRUnCMIYgZw5437zOenIR6nhKdTz+un69Ftf/MMmLh54vDDIWTn0K+pZ6LwYEsZFTD2wHZJRskrtgxlEQfMVR3CvKH1VgTyVhtJdRmsihByU8TY+j8Dj8DiA/a1PCmyh3jRkQQqvIJqlyltYDzC5iJT+MMh1ZJNtz+DghCiR6sWmaLUvez9PCsiPNkdwZoDFJ3kFri92R4HaVbCdmL3Ha27YRMHytx9yvHOTFSsKhE6ITDM2t6ZKdmsqprUI60Sghr1XcRi6di58e7ANRnxMP0MqMRpXVmJgzULXPIxQ4e2LkIPPBTg==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TEW/1tsNcghplI60jU9gfIGi/4jjgrYhn4uukqz++RA9xWWjmZfXgDi5Z/Ia0ZdUcM5NVvA7BX2Hy1dUR2AmRqo5zMbrQHeNWaIq64LtxjXyKzVfyhTgQ/93SKPPvfuXAifwsMl7xdnlgUGDw1uiwSU2sBUexRjuwsqDqR7hycWDRenXadZPdrqqkpY452cCzA+qjUOz/VGQKhr41abECNw4aktVoqmcQdgo82gGm+KdR+sYREXEwVRdGmQZNkL8LzuicmoAgU/M8UvokBTxFwzbUQ3a1RTmYaAJ25HYfQoiD6PfPq7qb4zJONxRVLtLg0appZO9y/F5KEbyMEFHoA==
- Authentication-results-original: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
- Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>
- Delivery-date: Wed, 04 May 2022 07:25:53 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
- Nodisclaimer: true
- Original-authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
- Thread-index: AQHYXtGhCQ41RL6ZvkCIAGwqzunCAq0Ndo4AgADcHgA=
- Thread-topic: [PATCH 2/3] xen/arm: Advertise workaround 1 if we apply 3
Hi Julien,
> On 3 May 2022, at 19:17, Julien Grall <julien@xxxxxxx> wrote:
>
> Hi Bertrand,
>
> On 03/05/2022 10:38, Bertrand Marquis wrote:
>> SMCC_WORKAROUND_3 is handling both Spectre v2 and spectre BHB.
>> So when a guest is asking if we support workaround 1, tell yes if we
>> apply workaround 3 on exception entry as it handles it.
>> This will allow guests not supporting Spectre BHB but impacted by
>> spectre v2 to still handle it correctly.
>> The modified behaviour is coherent with what the Linux kernel does in
>> KVM for guests.
>> While there use ARM_SMCCC_SUCCESS instead of 0 for the return code value
>> for workaround detection to be coherent with Workaround 2 handling.
>> Signed-off-by: Bertrand Marquis <bertrand.marquis@xxxxxxx>
>
> Acked-by: Julien Grall <jgrall@xxxxxxxxxx>
Thanks
>
> I think we should also consider for backport.
Agree.
Cheers
Bertrand
>
> Cheers,
>
> --
> Julien Grall
|
