From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 40578281525 for ; Tue, 13 Jan 2026 14:21:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.176.79.56 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768314071; cv=none; b=EbC9ETT+Lz82QFBR9wp/ZQuvfOdtYgHuIpRTxySWWandKxAWyt6wpin5zYIR5Q5LA/00mec3gutZQdh6IyVYEI6rS8ovEWW7mPBdGkjHFKoi8mFYqsbLKC989iUgcJhJGP03+mPdCiBuRe3EuY/gnpepmC6ESBV1pQKor+Kf/lc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768314071; c=relaxed/simple; bh=0BQWiz8SX07eje7WjPsQJTGhZVVXklD3eZ7nPpNNYVI=; h=Date:From:To:CC:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=EmJh63Z80RfKGhBmS7weDe+GRpPTdbldRKjLLMwuyq/eXRmOIclmzNThByzMyfD2AYcUga95Wa55/apJORoSL3Zv4Xgk7/ebseYb8Kvj5ZXFyY3pKl+CZatAiBRH24KgTYKn8vFCqJHrCxwgJqFfNVAeTyOZRvqSpYS+fKUJ6VU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=185.176.79.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.18.224.107]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4drBHT5c2LzJ46ZX; Tue, 13 Jan 2026 22:20:53 +0800 (CST) Received: from dubpeml100005.china.huawei.com (unknown [7.214.146.113]) by mail.maildlp.com (Postfix) with ESMTPS id D801340585; Tue, 13 Jan 2026 22:21:06 +0800 (CST) Received: from localhost (10.203.177.15) by dubpeml100005.china.huawei.com (7.214.146.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.36; Tue, 13 Jan 2026 14:21:05 +0000 Date: Tue, 13 Jan 2026 14:21:04 +0000 From: Jonathan Cameron To: Ben Horgan CC: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , Subject: Re: [PATCH v3 13/47] KVM: arm64: Use kernel-space partid configuration for hypercalls Message-ID: <20260113142104.00002641@huawei.com> In-Reply-To: <20260112165914.4086692-14-ben.horgan@arm.com> References: <20260112165914.4086692-1-ben.horgan@arm.com> <20260112165914.4086692-14-ben.horgan@arm.com> X-Mailer: Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-ClientProxiedBy: lhrpeml100009.china.huawei.com (7.191.174.83) To dubpeml100005.china.huawei.com (7.214.146.113) On Mon, 12 Jan 2026 16:58:40 +0000 Ben Horgan wrote: > On nVHE systems whether or not MPAM is enabled, EL2 continues to use > partid-0 for hypercalls, even when the host may have configured its kernel > threads to use a different partid. 0 may have been assigned to another > task. Copy the EL1 MPAM register to EL2. This ensures hypercalls use the > same partid as the kernel thread does on the host. > > Signed-off-by: Ben Horgan Reviewed-by: Jonathan Cameron > --- > Changes since v2: > Use mask > Use read_sysreg_el1 to cope with hvhe nvhe