[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230519161014.00003002@Huawei.com>
Date: Fri, 19 May 2023 16:10:14 +0100
From: Jonathan Cameron <Jonathan.Cameron@...wei.com>
To: Davidlohr Bueso <dave@...olabs.net>
CC: LiuLele <liu.lele@...com>, <dave.jiang@...el.com>,
<alison.schofield@...el.com>, <bhelgaas@...gle.com>,
<bwidawsk@...nel.org>, <dan.j.williams@...el.com>,
<helgaas@...nel.org>, <ira.weiny@...el.com>,
<linux-acpi@...r.kernel.org>, <linux-cxl@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-pci@...r.kernel.org>,
<rostedt@...dmis.org>, <vishal.l.verma@...el.com>
Subject: Re: CXL memory device not created correctly
On Thu, 18 May 2023 18:38:46 -0700
Davidlohr Bueso <dave@...olabs.net> wrote:
> On Fri, 19 May 2023, LiuLele wrote:
>
> >In my testing CXL device /sys/bus/cxl/devices/mem0 not created, and the get error messages :
> >
> >```
> >cxl_pci 0000:0d:00.0: Failed to get interrupt for event Info log
> >```
> >
> >My test environment is a qemu CXL emulator with qemu v8.0.0, Linux kernel v6.3.0.
> >While with kernel 5.9.13, /sys/bus/cxl/devices/mem0 can be created.
>
> Yes, this can be annoying and would argue the probe should not error out.
> Regardless, the actual qemu support is in Jonathan's tree:
>
> https://gitlab.com/jic23/qemu/-/commit/a04e6476df363d1f6bc160577b30dda6564d3f67
That just failed to make it into an upstream pull request today due to some
bugs in a the poison list set that came before it :(
v6 or poison list and events support are both on list now and hopefully will make
this QEMU cycle so be in 8.1
Jonathan
>
> Thanks,
> Davidlohr
Powered by blists - more mailing lists