[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251222140936.00007f38@huawei.com>
Date: Mon, 22 Dec 2025 14:09:36 +0000
From: Jonathan Cameron <jonathan.cameron@...wei.com>
To: <mhonap@...dia.com>
CC: <aniketa@...dia.com>, <ankita@...dia.com>, <alwilliamson@...dia.com>,
<vsethi@...dia.com>, <jgg@...dia.com>, <mochs@...dia.com>,
<skolothumtho@...dia.com>, <alejandro.lucero-palau@....com>,
<dave@...olabs.net>, <dave.jiang@...el.com>, <alison.schofield@...el.com>,
<vishal.l.verma@...el.com>, <ira.weiny@...el.com>,
<dan.j.williams@...el.com>, <jgg@...pe.ca>, <yishaih@...dia.com>,
<kevin.tian@...el.com>, <cjia@...dia.com>, <kwankhede@...dia.com>,
<targupta@...dia.com>, <zhiw@...dia.com>, <kjaju@...dia.com>,
<linux-kernel@...r.kernel.org>, <linux-cxl@...r.kernel.org>,
<kvm@...r.kernel.org>
Subject: Re: [RFC v2 08/15] vfio/cxl: discover precommitted CXL region
On Tue, 9 Dec 2025 22:20:12 +0530
mhonap@...dia.com wrote:
> From: Zhi Wang <zhiw@...dia.com>
>
> A type-2 device can have precommitted CXL region that is configured by
> BIOS. Before letting a VFIO CXL variant driver create a new CXL region,
> the VFIO CXL core first needs to discover the precommited CXL region.
This is similar to the discussion in Alejandro's type 2 series.
Before we put infrastructure in place for handling bios precommitting I'd
like some discussion of why they are doing that.
There are a few possible reasons, but in at least some cases I suspect it
is misguided attempt to set things up that the BIOS should be leaving
well alone. I'd also be curious to hear if the decoders are locked
or not in the systems you've seen it on? I.e. can we rip it down
and start again?
I'm definitely not saying we should not support this, but I want
people to enumerate the reasons they need it.
>
> Discover the precommited CXL region when enabling CXL devices.
>
> Signed-off-by: Zhi Wang <zhiw@...dia.com>
> Signed-off-by: Manish Honap <mhonap@...dia.com>
Powered by blists - more mailing lists