Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp423405ybt; Wed, 24 Jun 2020 02:40:04 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwxcpLNmjoaNqYtASFGX8ejtNTtUsBbZh6M9t2EbQVEaZsQI6ZGO/Us38izGAvjfzDpLWRJ X-Received: by 2002:a17:906:d9cd:: with SMTP id qk13mr24006697ejb.268.1592991604280; Wed, 24 Jun 2020 02:40:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592991604; cv=none; d=google.com; s=arc-20160816; b=lAvf/kmbNp6bSvM6uBh+wOsK7Xui+FKWS6Osw4HrBnbpmEpH/4+swEsg3a81xBdcAh 9HAIGdCdK6S8zUX+VHLiaxabErzi6lhyuPVeQGiZNoooxZ+fVPIsAe79IW3jlXYZ8PhM dW73FQYmdDAgCmiXQ4B0NIS9qdw/u4LLOOi10MPxYCq1NH2grAFLcnO9v/Zw/gErxfUX 0NVDprc8SZIEiNVx6A5d4rv7SrBueAjFgEE/6ij9PWjhNLuJqHQMF7RVvCaOxITZbKzx xM4deS47s8gCYv+QiS7tjOO61HBVSVTxXCkz5TNbTW2RHfB0y8o7tUcrurv8Fe80r9Nd qhkg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=t04pkHfntC6nS9MLvgcUt5qFCchxC54AEf1x+WJPkI0=; b=LDezrXP5t/LQ4Z1XOKe639IX5HkfOUgHtEFl55DAPfv9i47guh/7wcmNaw9XTNf1Fa 4CkD9EaGWAQ3UuilGvHYIITywSFh6TMUZzoRbf4ZJAaXLXoLBPQ7wQ8eyzZd/3wfVXAc T69sY2yS1pHaO8nwHPlsD+jyLuGWLoPgKfALlQcXFwbkSu3Frvl+Npa7i+KxF3qTRHAi nzk3cxPiliFEo9Mc+FoNbwueeBlJ8471gy0RipnmEwOhXxcYv7TnhC5tu0E1P9+nHmJP 01+3F9SgMX9BAr56GT3i0ycpvtwd6rlzQb1299i6PhoiT0gmjCwGtr2pKHm+u3Qv1Z5L r2bQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id cf29si13150260edb.419.2020.06.24.02.39.39; Wed, 24 Jun 2020 02:40:04 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389820AbgFXJiw (ORCPT + 99 others); Wed, 24 Jun 2020 05:38:52 -0400 Received: from foss.arm.com ([217.140.110.172]:53582 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388031AbgFXJiw (ORCPT ); Wed, 24 Jun 2020 05:38:52 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id AD8111FB; Wed, 24 Jun 2020 02:38:51 -0700 (PDT) Received: from gaia (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 68A463F73C; Wed, 24 Jun 2020 02:38:50 -0700 (PDT) Date: Wed, 24 Jun 2020 10:38:48 +0100 From: Catalin Marinas To: Peter Maydell Cc: Steven Price , Marc Zyngier , Will Deacon , Dave Martin , lkml - Kernel Mailing List , Thomas Gleixner , kvmarm@lists.cs.columbia.edu, arm-mail-list Subject: Re: [RFC PATCH 0/2] MTE support for KVM guest Message-ID: <20200624093846.GA11863@gaia> References: <20200617123844.29960-1-steven.price@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 23, 2020 at 07:05:07PM +0100, Peter Maydell wrote: > On Wed, 17 Jun 2020 at 13:39, Steven Price wrote: > > These patches add support to KVM to enable MTE within a guest. It is > > based on Catalin's v4 MTE user space series[1]. > > > > [1] http://lkml.kernel.org/r/20200515171612.1020-1-catalin.marinas%40arm.com > > > > Posting as an RFC as I'd like feedback on the approach taken. > > What's your plan for handling tags across VM migration? > Will the kernel expose the tag ram to userspace so we > can copy it from the source machine to the destination > at the same time as we copy the actual ram contents ? Qemu can map the guest memory with PROT_MTE and access the tags directly with LDG/STG instructions. Steven was actually asking in the cover letter whether we should require that the VMM maps the guest memory with PROT_MTE as a guarantee that it can access the guest tags. There is no architecturally visible tag ram (tag storage), that's a microarchitecture detail. -- Catalin