[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Recent patches break ACPI tables
From: |
Almudena Garcia |
Subject: |
Re: Recent patches break ACPI tables |
Date: |
Tue, 20 Jun 2023 09:41:41 +0000 |
El martes 20 de junio de 2023, Samuel Thibault escribió:
> Almudena Garcia, le lun. 19 juin 2023 18:35:51 +0000, a ecrit:
> > phystokv will doesn't solve fully the problem, because the lapic address is
> > out of the range allowed by this function.
>
> Ah, right.
>
> > Currently, we are using paging to map every ACPI table which we need to
> > access (to get a virtual address of this).
> >
> > But the search of the initial ACPI address is based in a physical address
> > range.
>
> Can't this be mapped with kmem_map_aligned_table as well?
>
> Samuel
>
I think that lapic is already mapped here. The problem is that there are some
CPU_NUMBER calls before lapic initialization.
--
Enviado desde mi dispositivo Sailfish
- Recent patches break ACPI tables, Damien Zammit, 2023/06/17
- Re: Recent patches break ACPI tables, Samuel Thibault, 2023/06/18
- Re: Recent patches break ACPI tables, luca, 2023/06/19
- Re: Recent patches break ACPI tables, Almudena Garcia, 2023/06/19
- Re: Recent patches break ACPI tables, luca, 2023/06/19
- Re: Recent patches break ACPI tables, Luca, 2023/06/19
- Re: Recent patches break ACPI tables, Almudena Garcia, 2023/06/19
- Re: Recent patches break ACPI tables, Damien Zammit, 2023/06/20
- Re: Recent patches break ACPI tables, Samuel Thibault, 2023/06/20
- Re: Recent patches break ACPI tables,
Almudena Garcia <=