Re: Problems in PV dom0 on recent x86 hardware

[Jason Andryuk <jason.andryuk@xxxxxxx>]

On 2024-07-16 10:43, Jan Beulich wrote:
> On 09.07.2024 15:08, Jason Andryuk wrote:
> > On 2024-07-09 06:56, Jürgen Groß wrote:
> > > On 09.07.24 09:01, Jan Beulich wrote:
> > > > On 09.07.2024 08:36, Jürgen Groß wrote:
> > > > > On 09.07.24 08:24, Jan Beulich wrote:
> > > > > > On 08.07.2024 23:30, Jason Andryuk wrote:
> > > > > > >     From the backtrace, it looks like the immediate case is just
> > > > > > > trying to
> > > > > > > read a 4-byte version:
> > > > > > >
> > > > > > >     >>>> [   44.575541]  ucsi_acpi_dsm+0x53/0x80
> > > > > > >     >>>> [   44.575546]  ucsi_acpi_read+0x2e/0x60
> > > > > > >     >>>> [   44.575550]  ucsi_register+0x24/0xa0
> > > > > > >     >>>> [   44.575555]  ucsi_acpi_probe+0x162/0x1e3
> > > > > > >
> > > > > > > int ucsi_register(struct ucsi *ucsi)
> > > > > > > {
> > > > > > >             int ret;
> > > > > > >
> > > > > > >             ret = ucsi->ops->read(ucsi, UCSI_VERSION, &ucsi->version,
> > > > > > >                                   sizeof(ucsi->version));
> > > > > > >
> > > > > > > ->read being ucsi_acpi_read()
> > > > > > >
> > > > > > > However, the driver also appears write to adjacent addresses.
> > > > > > There are also corresponding write functions in the driver, yes, but
> > > > > > ucsi_acpi_async_write() (used directly or indirectly) similarly calls
> > > > > > ucsi_acpi_dsm(), which wires through to acpi_evaluate_dsm(). That's
> > > > > > ACPI object evaluation, which isn't obvious without seeing the
> > > > > > involved AML whether it might write said memory region.
> > > > > I guess an ACPI dump would help here?
> > > > Perhaps, yes.
> > > It is available in the bug report:
> > >
> > > https://bugzilla.opensuse.org/show_bug.cgi?id=1227301
> > After acpixtract & iasl:
> >
> > $ grep -ir FEEC *
> > dsdt.dsl:   OperationRegion (ECMM, SystemMemory, 0xFEEC2000, 0x0100)
> > ssdt16.dsl: OperationRegion (SUSC, SystemMemory, 0xFEEC2100, 0x30)
> As I look to have only flawed variants of acpixtract to hand, any chance
> you could supply me with dsdt.dsl and all ssdt*.dsl that you successfully
> extracted / disassembled?
Sure thing.  There are a lot - all attached.

Regards,
Jason

Attachment: dsdt.dsl
Description: Text Data

Attachment: ssdt1.dsl
Description: Text Data

Attachment: ssdt2.dsl
Description: Text Data

Attachment: ssdt3.dsl
Description: Text Data

Attachment: ssdt4.dsl
Description: Text Data

Attachment: ssdt5.dsl
Description: Text Data

Attachment: ssdt6.dsl
Description: Text Data

Attachment: ssdt7.dsl
Description: Text Data

Attachment: ssdt8.dsl
Description: Text Data

Attachment: ssdt9.dsl
Description: Text Data

Attachment: ssdt10.dsl
Description: Text Data

Attachment: ssdt11.dsl
Description: Text Data

Attachment: ssdt12.dsl
Description: Text Data

Attachment: ssdt13.dsl
Description: Text Data

Attachment: ssdt14.dsl
Description: Text Data

Attachment: ssdt15.dsl
Description: Text Data

Attachment: ssdt16.dsl
Description: Text Data

Attachment: ssdt17.dsl
Description: Text Data

Attachment: ssdt18.dsl
Description: Text Data

Attachment: ssdt19.dsl
Description: Text Data

Attachment: ssdt20.dsl
Description: Text Data

Attachment: ssdt21.dsl
Description: Text Data

Attachment: ssdt22.dsl
Description: Text Data

Attachment: ssdt23.dsl
Description: Text Data

Attachment: ssdt24.dsl
Description: Text Data