Re: [PATCH v5 08/16] acpi/ghes: don't check if physical_address is not zero
From: Jonathan Cameron
Date: Mon Dec 09 2024 - 05:15:18 EST
On Wed, 4 Dec 2024 14:12:46 +0100
Igor Mammedov <imammedo@xxxxxxxxxx> wrote:
> On Wed, 4 Dec 2024 08:41:16 +0100
> Mauro Carvalho Chehab <mchehab+huawei@xxxxxxxxxx> wrote:
>
> > The 'physical_address' value is a faulty page. As such, 0 is
> > as valid as any other value.
I'm not sure what a 'faulty page' is. but code looks fine.
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@xxxxxxxxxx>
> >
> > Suggested-by: Igor Mammedov <imammedo@xxxxxxxxxx>
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@xxxxxxxxxx>
>
> Reviewed-by: Igor Mammedov <imammedo@xxxxxxxxxx>
>
> > ---
> > hw/acpi/ghes.c | 4 ----
> > 1 file changed, 4 deletions(-)
> >
> > diff --git a/hw/acpi/ghes.c b/hw/acpi/ghes.c
> > index edc74c38bf8a..a3dffd78b012 100644
> > --- a/hw/acpi/ghes.c
> > +++ b/hw/acpi/ghes.c
> > @@ -400,10 +400,6 @@ int acpi_ghes_record_errors(uint16_t source_id, uint64_t physical_address)
> >
> > start_addr = le64_to_cpu(ags->ghes_addr_le);
> >
> > - if (!physical_address) {
> > - return -1;
> > - }
> > -
> > start_addr += source_id * sizeof(uint64_t);
> >
> > cpu_physical_memory_read(start_addr, &error_block_addr,
>
>