From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 A3256199FB0 for ; Fri, 21 Aug 2026 22:37:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787351840; cv=none; b=W+QOEGOOpnRJfUVguyBAH2AseEQmapY4KN4nS0qzG1AI7BJ3nsfzeML/0fzswP/t6QfyEb/VPsKjtqNR4+QZf31h0icJGDKyowU5FgRY4gwC0DxHvKivja1yyJ56dpr99Zk+Hkf54/Cc6M07QZoqZFxIdF/hWiIHOtcXhTNG250= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787351840; c=relaxed/simple; bh=HOWCs9Kh1nwN9hGcJEtDASQDXG+0AMIA1EZioJFE01g=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=UZTQkwzCNZwPbfgdQTmHG3rb5iSUx6dQTsOA0fl0cfS5XUfan/s+UPUI/IQwzN0Z/dex3iTqS2dlmX4hS4y4o5WsfV4x99ZjlmMb1Xfg7ZNCqHmNzhI807TjOyJX7uFH/zB2bHij8KKprEh6j6SV3vxMYZ03JpjMCDu1LhiL65w= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=j2szDHWL; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="j2szDHWL" Received: by smtp.kernel.org (Postfix) with ESMTPSA id CDA991F000E9; Fri, 21 Aug 2026 22:37:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1787351839; bh=AjxOqaaKTZuUzeffhliIsQXqyUZYGGdIf8bpAmKghM4=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=j2szDHWLvH4QVTs/NSezPKkvLdHO55H3eO8MBvViWT8dWabrNs4Li9ZErDL1LD+m4 U/yW3x+xFj7F4KTb6d4VMpWWRofXeXJTKAGy+7pPMfgMlx0GPwNqZxCjlNZgwmetTN x/xdIaKLtd5lV8El6mr8U9rZvmbE43cz7mtKO02d3Eh7lFrEajFlvstwR/mAY0WxID R7TNWw8NmPwHoSZ18RwowVAOpKuNflNqfJEhrLygo6+Nl89uTgqCK1coa1fnLLrbAH TjqQw90AvZ9UPcf49dJmFT7nhHJsx3engECL6mWwHytSZpr8/ekeccevccyMlvLUls iB4lYCrUlpAVw== Date: Fri, 21 Aug 2026 23:37:14 +0100 From: Jonathan Cameron To: Guixin Liu Cc: Davidlohr Bueso , Dave Jiang , Alison Schofield , Vishal Verma , Dan Williams , Ira Weiny , Li Ming , linux-cxl@vger.kernel.org Subject: Re: [PATCH v4] cxl/pci: Skip reset detection for DVSEC emulated decoders Message-ID: <20260821233714.54f67d0a@jic23-huawei> In-Reply-To: <20260821233305.32d77d60@jic23-huawei> References: <20260821021029.2550584-1-kanie@linux.alibaba.com> <20260821233305.32d77d60@jic23-huawei> X-Mailer: Claws Mail 4.4.0 (GTK 3.24.52; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: linux-cxl@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Fri, 21 Aug 2026 23:33:05 +0100 Jonathan Cameron wrote: > On Fri, 21 Aug 2026 10:10:29 +0800 > Guixin Liu wrote: > > > After an FLR or SBR, __cxl_endpoint_decoder_reset_detected() samples the > > Committed bit at cxlhdm->regs.hdm_decoder for every decoder that has > > CXL_DECODER_F_ENABLE set. Decoders emulated from the CXL DVSEC range > > registers carry that flag too, but their state does not live in the HDM > > decoder registers. When the component registers expose no HDM decoder > > capability, regs.hdm_decoder is NULL and the readl() oopses in the reset > > completion path. When the capability is present but firmware left > > Mem_Enable set with the global HDM decoder enable clear, the Committed bit > > reads zero and cxl_reset_done() reports a reset that never happened: it > > taints the kernel and strips CXL_DECODER_F_ENABLE and CXL_DECODER_F_LOCK > > from every endpoint decoder, even though the driver still cannot reprogram > > the DVSEC ranges. > > > > Skip the check when cxld->commit is NULL. Only > > cxl_setup_hdm_decoder_from_dvsec() leaves that callback unset, so that one > > test covers both emulation paths, and a DVSEC-described range has no > > Committed bit for a reset to clear. > > > This is still a lot of text to read - I'll have stab an what I think would be sufficient. > Take this perhaps as inspiration, not a precise suggestion! Ah I see this was the cut down text Dave suggested. That's fine (though I think he could have gone further!) Reviewed-by: Jonathan Cameron I think it is still worth thinking about the question on what it means to try and recover below. Though looking at how this is used, it is just to complain that something crazy happened - so maybe none of this matters! Jonathan > > When HDM decoders are emulated from DVSEC range registers either (a) there are > no HDM decoder registers present or (b) the DVSEC registers were in use at driver > load. > > After FLR or SBR, __cxl_endpoint_decoder_reset_detected() checks the HDM > decoder committed bit for any previously committed decoders. This includes > emulated decoders: (a) results in a NULL pointer dereference, (b) in a false > detection of reset when they are present and not in use as the committed bit > was never set. > > Use absence of cxld->commit to elide the reset check for emulated decoders. > > > Fixes: 934edcd436dc ("cxl: Add post-reset warning if reset results in loss of previously committed HDM decoders") > > Signed-off-by: Guixin Liu > > This does make me wonder if we should be doing something similar to check > the dvsec based decoding reset. The memory_base_high should reset to 0 > for example. > > Can we actually do anything with such devices? Not sure we can today. > That is not a reason to crash however so this fix still makes sense. > > Jonathan > > > --- > > This was patch 4/8 of the "cxl: Assorted fixes" series [1], resent > > individually per review feedback. > > > > > The two synchronisation concerns the review bot raised on v2 - the missing > > exclusion against a cxl_port unbind freeing the devm allocated cxl_hdm, and > > the plain read-modify-write of cxld->flags in > > cxl_endpoint_decoder_clear_reset_flags() while the region paths update the > > same word under cxl_rwsem.region - are still untouched here. Both are > > about the reset handler's locking rather than about which registers it > > reads, and neither fix is local; happy to follow up with separate patches. > > > > v1->v2: > > - rebase onto cxl/next > > - rewrite the commit message to describe the behaviour rather than narrate > > the code change (Alison Schofield) > > > > v2->v3: > > - test cxld->commit instead of cxlhdm->regs.hdm_decoder, so that decoders > > emulated from the DVSEC ranges are also skipped when the HDM decoder > > registers exist but are globally disabled (Richard Cheng) > > - update the subject and the commit message for the widened scope > > > > v3->v4: > > - shorten the commit message (Dave Jiang) > > > > [1] https://lore.kernel.org/linux-cxl/20260811113608.2815625-1-kanie@linux.alibaba.com/ > > > > drivers/cxl/core/pci.c | 7 +++++++ > > 1 file changed, 7 insertions(+) > > > > diff --git a/drivers/cxl/core/pci.c b/drivers/cxl/core/pci.c > > index 9d807c1a002c..d8b07f86bab0 100644 > > --- a/drivers/cxl/core/pci.c > > +++ b/drivers/cxl/core/pci.c > > @@ -683,6 +683,13 @@ static int __cxl_endpoint_decoder_reset_detected(struct device *dev, void *data) > > if ((cxld->flags & CXL_DECODER_F_ENABLE) == 0) > > return 0; > > > > + /* > > + * Decoders emulated from the DVSEC range registers have no commit > > + * callback and no HDM decoder registers to consult. > > + */ > > + if (!cxld->commit) > > + return 0; > > + > > cxlhdm = dev_get_drvdata(&port->dev); > > hdm = cxlhdm->regs.hdm_decoder; > > ctrl = readl(hdm + CXL_HDM_DECODER0_CTRL_OFFSET(cxld->id)); > > > > base-commit: 7098e9cd98a05c0c5de2fae0c2465f9d966fdd07 > >