From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 744D42D0C9A for ; Thu, 14 May 2026 19:21:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778786480; cv=none; b=kUx/nsmz6S37WikWWbPeDKzf4RHBs2fE4+jl/91j+SDPg2IXS8cTw7yX+r0AbNDwqCJadbh0iKOf/+AhFZXhlhB7OfKVwsZHhlFgpk4ghVzb/edXIK0KaNNoRcgRcCM2ekb1Lusjf2da6PDHHhG5G3kxtgp0lqyJylCSpGgyHXI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778786480; c=relaxed/simple; bh=Va3cRIqxQSKxvQEeE0XaT93j2ztCyW0k4rs+TRIemlA=; h=Date:From:To:Cc:Message-ID:In-Reply-To:References:Subject: Mime-Version:Content-Type; b=cfRrzL5WuGJMmHgHrIly0uwxZLCsAUurUEdvVuqpJVpNh7wIXQGvQCQNmdc5+Nd5SJwdWNe5mSOJLNLdTSt8xD77S/9YV/o8Ewbs3EsIXZbDsyWvdnCQmKpw3tX5tJfvTWhCrn9Te3juc91Nu2r+npYXXHbcqTWpuEC8F+GAeQ4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=KGreEjW9; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="KGreEjW9" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 451BEC4AF0B; Thu, 14 May 2026 19:21:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1778786480; bh=Va3cRIqxQSKxvQEeE0XaT93j2ztCyW0k4rs+TRIemlA=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=KGreEjW9SZq1lEVghygx3QlFfOq55ZwKplpFm00DjZhAQtKJZjE53H+KmdTDeJVFM xY4avFIOk+7TnGKLpv6HW3A6VckM28JG8bZhNAjl/hTbc/WfWKq+NHCMi18BafJ7TH GXLrCxvEBLe8FK2hkqRL4X9trjuzOXgIKals1rQ5C5uxp6YyUGaDnelFob6pbBog+I tsXYRpV8FZXiXjd5rE1kSq2JIBDdtvrhQFWxUWp1dTusHIF/lNSD7s5HPbkK0iL7Cs f88g2Sy75YgOqSIlE4PPmKp4kltCBKnHmGYh0nc0bC0FqIi4MWCudhbS4LAnkSmk/J GRgc3grd6ZK5g== Received: from phl-compute-02.internal (phl-compute-02.internal [10.202.2.42]) by mailfauth.phl.internal (Postfix) with ESMTP id 88BBAF40068; Thu, 14 May 2026 15:21:18 -0400 (EDT) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-02.internal (MEProxy); Thu, 14 May 2026 15:21:18 -0400 X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefhedrtddtgdduvdekfeehucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurhepfffhvfevkfgjfhfugggtgfesthejredttddtjeenucfhrhhomhepfdffrghnucgh ihhllhhirghmshculdhnvhhiughirgdmfdcuoegujhgsfieskhgvrhhnvghlrdhorhhgqe enucggtffrrghtthgvrhhnpedvgeehieekteelueffueehfeejjedvjedvveetfefgffev hedvuedvffevffdvheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpegujhgsfidomhgvshhmthhprghuthhhphgvrhhsohhnrghlihhthidqudej jedvfedtgeehhedqfeeffeelgedtgeejqdgujhgsfieppehkvghrnhgvlhdrohhrghesfh grshhtmhgrihhlrdgtohhmpdhnsggprhgtphhtthhopedvhedpmhhouggvpehsmhhtphho uhhtpdhrtghpthhtohepughjsgifsehkvghrnhgvlhdrohhrghdprhgtphhtthhopehsmh grughhrghvrghnsehnvhhiughirgdrtghomhdprhgtphhtthhopegshhgvlhhgrggrshes ghhoohhglhgvrdgtohhmpdhrtghpthhtohepuggrnhdrjhdrfihilhhlihgrmhhssehinh htvghlrdgtohhmpdhrtghpthhtohepuggrvhgvrdhjihgrnhhgsehinhhtvghlrdgtohhm pdhrtghpthhtohepjhhonhgrthhhrghnrdgtrghmvghrohhnsehhuhgrfigvihdrtghomh dprhgtphhtthhopehirhgrrdifvghinhihsehinhhtvghlrdgtohhmpdhrtghpthhtohep vhhishhhrghlrdhlrdhvvghrmhgrsehinhhtvghlrdgtohhmpdhrtghpthhtoheprghlih hsohhnrdhstghhohhfihgvlhgusehinhhtvghlrdgtohhm X-ME-Proxy: Feedback-ID: i67ae4b3e:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 14 May 2026 15:21:17 -0400 (EDT) Date: Thu, 14 May 2026 12:21:16 -0700 From: "Dan Williams (nvidia)" To: "Dan Williams (nvidia)" , smadhavan@nvidia.com, bhelgaas@google.com, dan.j.williams@intel.com, dave.jiang@intel.com, jonathan.cameron@huawei.com, ira.weiny@intel.com, vishal.l.verma@intel.com, alison.schofield@intel.com, dave@stgolabs.net Cc: alwilliamson@nvidia.com, jeshuas@nvidia.com, vsethi@nvidia.com, skancherla@nvidia.com, vaslot@nvidia.com, sdonthineni@nvidia.com, mhonap@nvidia.com, vidyas@nvidia.com, jan@nvidia.com, mochs@nvidia.com, dschumacher@nvidia.com, linux-cxl@vger.kernel.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Srirangan Madhavan Message-ID: <6a0620acec806_57ad71008c@djbw-dev.notmuch> In-Reply-To: <6a03e5c099d98_123a100e3@djbw-dev.notmuch> References: <20260306092322.148765-1-smadhavan@nvidia.com> <20260306092322.148765-6-smadhavan@nvidia.com> <6a03e5c099d98_123a100e3@djbw-dev.notmuch> Subject: Re: [PATCH v5 5/7] cxl: Add CXL DVSEC reset sequence and flow orchestration 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=utf-8 Content-Transfer-Encoding: 7bit Dan Williams (nvidia) wrote: > smadhavan@ wrote: [..] A follow-up/// > In the short term the fastest answers to those questions is just walk > the memdev and cxl root, in the longer term I would be open to building > more CXL awareness into the core so that CXL reset does not need a > driver loaded. While I do think cxl_memdev attach is required for now, I do not think the UABI should suffer a move if the plan is to ever support more CXL awareness in the PCI core. It is also the case that PCI in general wants all PCI device relative attributes to be statically defined in pci_dev_attr_groups. What I think this wants then is something like a "cxl" attribute group whose visibility for now depends on the CXL core to invoke sysfs_update_group(s) when a cxl_memdev is registered. Then we can start to build the built-in CXL infrastructure that a driver-less "CXL reset" capability would need. I think this looks like HDM address space discovery is separated from 'struct cxl_decoder' object creation and the CXL core learns to reference the common / built-in HDM address space discovery. The main semantic we need is that anything that tries to map CXL memory needs to wait for a pending reset, and that reset needs to be blocked if CXL memory is mapped.