From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) (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 C48C632E13D for ; Thu, 18 Dec 2025 12:06:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=205.220.168.131 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766059611; cv=none; b=mZlbv0S20IO8lg3uyFEI/zNDsU4YSPRL0vO18ry/rH+nRHUm7kCH0qwrn1ZCl8pDJmftg3AzAPwjYJO/RgBa9btw2Kt77wVxBczFN4HiC26AB5y5NQE4pyIBaBei5K0wX5kw/ynqrg04tqts9VP614qPrYAKx/553WhmWBo1iFU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766059611; c=relaxed/simple; bh=XUQCtdy56jkLeN6CjpmFNuiQWWwM5ULplRmS1emubf4=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=dRcD4k9Zr9qfiBrD71vGpIQnpG1qvwrBO4JTdlkWeNpMTBxYTib0ZGN5UwscBcic6KoTAOjsUomk32P/KPX00dNB7q7/0k8Nqi3/2p5q7hkrJBVxEID9jFDMC1iZpKWQXcFnJiFcjOBeddWS9Z5hUDYaXkoMy5c0hX4f+JiNmW4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com; spf=pass smtp.mailfrom=oss.qualcomm.com; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b=EKl86Ush; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b=c41JSnEv; arc=none smtp.client-ip=205.220.168.131 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b="EKl86Ush"; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b="c41JSnEv" Received: from pps.filterd (m0279862.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 5BI9JT1w174259 for ; Thu, 18 Dec 2025 12:06:49 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qualcomm.com; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to; s=qcppdkim1; bh= tZnUSUtwe2m6/hm5+PNmIW5JMIFSGKcxs4eESP2A6y4=; b=EKl86Ush7TKUOEgq 831rDXftpYGxQKfCpMm5QhAzeTCqmdCiC+gzBoiWWOz+w3UMx7RIJj/OsqkgzuVd grc2v5dnLO0fRYd9Vgjd6I82fTp1p7B4zRpf7bFOvWwdNtCyKntSGYTwoaet5Og7 Cf1u69vGNdHkzQs5FTe5fPkHykHVxyu5hlQonZNQMshGLoVn+TxuTyOuEfz6XmmA z2X6Qf5ggTNd02v1pt+NeP0bRWP3NcOf4y7UtWM8U0m5+G6X0pstqERy1MhP/zyd YcpZoj4lecOQgFJ9hzSwntDc2P9eh10Ode7zmYn2u94bee3i8oUnk74Sij5qONVe 4INH8Q== Received: from mail-qt1-f200.google.com (mail-qt1-f200.google.com [209.85.160.200]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 4b43nmthmr-1 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Thu, 18 Dec 2025 12:06:48 +0000 (GMT) Received: by mail-qt1-f200.google.com with SMTP id d75a77b69052e-4ee409f1880so1219521cf.1 for ; Thu, 18 Dec 2025 04:06:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oss.qualcomm.com; s=google; t=1766059608; x=1766664408; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=tZnUSUtwe2m6/hm5+PNmIW5JMIFSGKcxs4eESP2A6y4=; b=c41JSnEvubJEsKQUdqzSe2cXTYovNszy6DXzZUHfY+oP76dlyeoPYDkagTzxrA5R/d wnO5SY0A+hWet7Svf+/0lZUpjB1ZYOzqJwHwTqii/uqppsnV7Jv4JSQhcCv8Am96MgLG yRdQUsWymp2sM2EFwQoi5hk8cLWbMudvWcHd1JEqjtO9IWg13K4VVNu3pu8E5xu8FxFu 4FhgjpM2BwWdWbIl6tbIpLjZJ4WoRX4x6mRR8CzZpGhdiQ8os4/LHN99Yu9k6MD+wxtN dRWzBZUxHl5iG6AF/xVh1I8yhaqa5WZC8oskrZ3XDDwL1cGd9CoElFGbbC7KeHFPoarF dF/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1766059608; x=1766664408; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=tZnUSUtwe2m6/hm5+PNmIW5JMIFSGKcxs4eESP2A6y4=; b=u07pPBN4bT6joc5jRQCknQ+RrRhumqYxuoMt1Bi2H2RdB0C/8VSrdRek4xleJ8/jKA dmDXB95UfmNcPNrXD3+p+M2Zug9qyPyREZ4KW3QjL+rwLstSlmp0I2l6E3sL6U8K2keq Cba+FWWDwiMsiIiOnk0OmiQTslErOh4lYbelvMwK4QgEd9KPAGUbdFBqZVv7NI4nZcAG zkHnIAczZ0Ixh3ZjGdfZs60yrNYqlrgfMqX+vXHWmhxWZHKtS4o+oyUPr4GBRRY4ovcV 4i7kJIP7wM0rU/o65SFsUYpLrGNRuI1QrnwaZDhIj6jU3pBcI+L0J4BX6fQOdr+YaR3K SWSg== X-Forwarded-Encrypted: i=1; AJvYcCVxjygipINJZjNHSlH/daaQp+3TkS4HnAUoJm9sWpGaKP8jmPJDz0VGBXYC7ZisaZd5yh+fy+ppKK98zRE=@vger.kernel.org X-Gm-Message-State: AOJu0YzLPmhHWdxdIWek0RLuBI4QfnVaqdhIDQ/Fteiat1C5dLgJc/JS 98GJbpzeECyDe1MHdJfo57Cqcg4o6EQsd02VBsRcwvKaUx/JLoU2LJrMvqTMrQ2o3TzWjjxxmyZ knImxTdRVpPnYQkp6/Ee+O+AoAAUQURBeUtZ8DyXzAwA8kGnCZLyHvSwMDSRK/uhbf8M= X-Gm-Gg: AY/fxX4zmn8XOjLDlrGkuYXFGyrEKggaNNzJdz9VKwqlaeMDxvy/gC+4kpXabuEgC1u 2LrKYa9zMkRWT/IUJnEyeX7TGjZMnyT/Vl0b4/zSpr6rWtOue0rbhKxAfjKcev0weyfvjkIQ+H4 XnHaXo4NIZzrIsGWQ0xK4rShMF8GuqLcfzndUvLKgtDzaci4PM6KxwjGAa8KZVz1Bd/bCVUsPyo x7ddx9o3r2sv29/QtBzDepnHpVwW2CY5Eo5M1i/bDok1camHRQQW2d3Yh52YYigBPnr6AIpC7Wx lIpHB+NcgcNb8xzH5wRtmaIMu9JnvMUNIqHPsxFJUQ99/+Dy1+JsVSMqQXq92W6Bvm2J1G5/TrJ Ig/AyMc/p6SOMB1R7iUS43kOgFZB4nmzVLEEHOmXwTpN2UWSy/HBIEAForY2z9hUYwg== X-Received: by 2002:ac8:5d07:0:b0:4e8:a54d:cce8 with SMTP id d75a77b69052e-4f3610c2804mr17836181cf.4.1766059607879; Thu, 18 Dec 2025 04:06:47 -0800 (PST) X-Google-Smtp-Source: AGHT+IEF+09EZkGiN7a1LxeerZG2n1/FnP21wZ/oFt4W9TqyZh08+f+1E8eRBAr3bsry0SLvh5dWfA== X-Received: by 2002:ac8:5d07:0:b0:4e8:a54d:cce8 with SMTP id d75a77b69052e-4f3610c2804mr17835451cf.4.1766059607252; Thu, 18 Dec 2025 04:06:47 -0800 (PST) Received: from [192.168.119.72] (078088045245.garwolin.vectranet.pl. [78.88.45.245]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-b80234a2ee4sm208657266b.57.2025.12.18.04.06.44 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 18 Dec 2025 04:06:46 -0800 (PST) Message-ID: Date: Thu, 18 Dec 2025 13:06:43 +0100 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v18 0/5] iommu/arm-smmu: introduction of ACTLR implementation for Qualcomm SoCs To: Charan Teja Kalla , Bibek Kumar Patro , Enric Balletbo i Serra Cc: robdclark@gmail.com, will@kernel.org, robin.murphy@arm.com, joro@8bytes.org, jgg@ziepe.ca, jsnitsel@redhat.com, robh@kernel.org, krzysztof.kozlowski@linaro.org, quic_c_gdjako@quicinc.com, dmitry.baryshkov@linaro.org, iommu@lists.linux.dev, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Maxime Ripard , Eric Chanudet References: <20241212151402.159102-1-quic_bibekkum@quicinc.com> <33826089-54b5-47bc-8a5b-6004c7a276b8@oss.qualcomm.com> <5a1aaf4a-c5d5-42e1-9044-d12a6c231904@oss.qualcomm.com> <1db3d7f5-0cdf-449c-bbc3-dc40c89ab27f@oss.qualcomm.com> Content-Language: en-US From: Konrad Dybcio In-Reply-To: <1db3d7f5-0cdf-449c-bbc3-dc40c89ab27f@oss.qualcomm.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Proofpoint-GUID: PAoplEi_cRiYfTbnF_Q5qIwOxZa0VdAz X-Proofpoint-Spam-Details-Enc: AW1haW4tMjUxMjE4MDEwMCBTYWx0ZWRfXxeCMl/RuLFnn 67MXcVhVTYAB+wW7hWHjoKgiZ/twhGrU1wKWz5K44tZ/uJnY8JsxrgUER6p6DtiigTYOqoSZP9M I70IO6ZPQrfs3w+coubIj1IuLqIlGeF6PWpSrpVkfkNImoTL9T3e7/oTi22F+jVoPcubJeRPg9F RTX3TJbZ2vts/mkM1WkZMIgdwpapTb6y+opLU5Vmhjrs/LuOpU6NLqmSAJoGGqOXWDtzDPBFXDZ E/5HceJu914/pLh9Ooil91klsOZxmaGSwbWzJg+aLfE/0DtiwXBAiBknBah2rNjXa0f8yVH9IPl YUJg5MGnCUje8Dsx5TWvUDCQcf9C8Ji3qAVTseNEOsg2FjLSa06DlWPwBAc4kfjeqr+PAXi7eQX yTWa3KnLVNmiV2tNeDDHYlEtD6/New== X-Proofpoint-ORIG-GUID: PAoplEi_cRiYfTbnF_Q5qIwOxZa0VdAz X-Authority-Analysis: v=2.4 cv=A6Zh/qWG c=1 sm=1 tr=0 ts=6943ee58 cx=c_pps a=JbAStetqSzwMeJznSMzCyw==:117 a=FpWmc02/iXfjRdCD7H54yg==:17 a=IkcTkHD0fZMA:10 a=wP3pNCr1ah4A:10 a=s4-Qcg_JpJYA:10 a=VkNPw1HP01LnGYTKEx00:22 a=VwQbUJbxAAAA:8 a=EUspDBNiAAAA:8 a=GtmQsnjonZUfJvkuU48A:9 a=3ZKOabzyN94A:10 a=QEXdDO2ut3YA:10 a=uxP6HrT_eTzRwkO_Te1X:22 X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.9,FMLib:17.12.100.49 definitions=2025-12-18_01,2025-12-17_02,2025-10-01_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 malwarescore=0 clxscore=1015 impostorscore=0 priorityscore=1501 spamscore=0 bulkscore=0 suspectscore=0 phishscore=0 lowpriorityscore=0 adultscore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2510240001 definitions=main-2512180100 On 11/13/25 2:55 PM, Charan Teja Kalla wrote: > > > On 11/12/2025 7:04 PM, Konrad Dybcio wrote: >>> Hi Eric, >>> >>> If a device has multiple SIDs, all serving the same functionality and grouped under the same "iommus" field, for example: >>> >>> iommus = <&apps_smmu, 0x2141, 0x0>, >>>           <&apps_smmu, 0x25c1, 0x0>, >>>           <&apps_smmu, 0x2161, 0x0>; >>> >>> In this case, all the SIDs will be associated with the same context bank. Even if the three SIDs have different ACTLR settings, since SMMU_CB_ACTLR is per CB setting, all SIDs attached to that bank will share the same ACTLR configuration. This is why we designed it to be "per device / per compatible". >> Does that suggest the settings may be slightly suboptimal? I don't understand your question > Or it is limitation to use the ACTLR? > >> There's some work being done to allow more granular association of >> the passed SIDs: >> >> https://lore.kernel.org/linux-arm-msm/20250928171718.436440-1- >> charan.kalla@oss.qualcomm.com/ > Sorry, I am unable to link this limitation for actlr setting with the > work. Can you elaborate please? Because your email client is misconfigured and it broke the line.. If it's thunderbird, pretty sure we have a "change these configs" type section on go/upstream, please take a look > IIUC, unless the SIDs are totally separated per actlr settings and > attached to CB(which are limited), this can't be achieved...but may be a > question here to check is it really a __valid__ to associate a different > actlr settings SID to use the same CB? The last question you asked is certainly a valid one But I was wondering if iommu-map could be useful to resolve this, where we choose an abstract set of function IDs and then handle the IOMMU configuration manually, based on the func_id-delimited sets: iommu-map = , , , ; But perhaps that's more useful from the driver-that-handles-the-device perspective Konrad