All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Jeremy Linton <jeremy.linton@arm.com>,
	Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
	Rob Herring <robh+dt@kernel.org>, Christoph Hellwig <hch@lst.de>,
	Robin Murphy <robin.murphy@arm.com>,
	Hanjun Guo <guohanjun@huawei.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Anshuman Khandual <anshuman.khandual@arm.com>
Subject: Re: [PATCH] arm64: mm: set ZONE_DMA size based on early IORT scan
Date: Tue, 13 Oct 2020 14:13:46 +0100	[thread overview]
Message-ID: <20201013131346.GA20925@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <CAMj1kXEbZ3cN1N2V6MfbUZsTot+9TsLTC_UMm5JP1OW8AwvuOw@mail.gmail.com>

On Tue, Oct 13, 2020 at 01:22:32PM +0200, Ard Biesheuvel wrote:

[...]

> > > diff --git a/Documentation/arm64/arm-acpi.rst b/Documentation/arm64/arm-acpi.rst
> > > index 47ecb9930dde..947f5b5c45ef 100644
> > > --- a/Documentation/arm64/arm-acpi.rst
> > > +++ b/Documentation/arm64/arm-acpi.rst
> > > @@ -205,6 +205,13 @@ devices available.  This list of tables is not meant to be all inclusive;
> > >  in some environments other tables may be needed (e.g., any of the APEI
> > >  tables from section 18) to support specific functionality.
> > >
> > > +It is assumed that all DMA capable devices in the system are able to
> > > +access the lowest 4 GB of system memory. If this is not the case, an
> > > +IORT describing those limitations is mandatory, even if an IORT is not
> > > +otherwise necessary to describe the I/O topology, and regardless of
> > > +whether _DMA methods are used to describe the DMA limitations more
> > > +precisely. Once the system has booted, _DMA methods will take precedence
> > > +over DMA addressing limits described in the IORT.
> >
> > If this is a boot requirement it must be in ARM's official documentation,
> > first, not the kernel one.
> >
> > I understand this is an urgent (well - no comments on why bootstrapping
> > ACPI on Raspberry PI4 is causing all this fuss, honestly) fix but that's
> > not a reason to rush through these guidelines.
> >
> > I would not add this paragraph to arm-acpi.rst, yet.
> >
> 
> Which documentation? ACPI compliance by itself is not sufficient for a
> system to be able to boot Linux/arm64, which is why we documented the
> requirements for ACPI boot on Linux/arm64 in this file. I don't think
> we need endorsement from ARM to decide that odd platforms like this
> need to abide by some additional rules if they want to boot in ACPI
> mode.

I think we do - if we don't we should not add this documentation either.

ACPI on ARM64 software stack is based on standardized HW requirements.
The sheer fact that we need to work around a HW deficiency shows that
either this platform should have never been booted with ACPI or the _HW_
design guidelines (BSA) are not tight enough.

Please note that as you may have understood I asked if we can implement
a workaround in IORT because that's information that must be there
regardless (and an OEM ID match in arch code - though pragmatic -
defeats the whole purpose), I don't think we should tell Linux kernel
developers how firmware must be written to work around blatantly
non-compliant systems.

Thanks,
Lorenzo

> > >  ACPI Detection
> > >  --------------
> > > diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
> > > index f0599ae73b8d..829fa63c3d72 100644
> > > --- a/arch/arm64/mm/init.c
> > > +++ b/arch/arm64/mm/init.c
> > > @@ -191,6 +191,14 @@ static void __init zone_sizes_init(unsigned long min, unsigned long max)
> > >       unsigned long max_zone_pfns[MAX_NR_ZONES]  = {0};
> > >
> > >  #ifdef CONFIG_ZONE_DMA
> > > +     if (IS_ENABLED(CONFIG_ACPI)) {
> > > +             extern unsigned int acpi_iort_get_zone_dma_size(void);
> >
> > Yes as Catalin asked please add a declaration in IORT headers.
> >
> 
> Ack.
> 
> > > +             zone_dma_bits = min(zone_dma_bits,
> > > +                                 acpi_iort_get_zone_dma_size());
> > > +             arm64_dma_phys_limit = max_zone_phys(zone_dma_bits);
> > > +     }
> > > +
> > >       max_zone_pfns[ZONE_DMA] = PFN_DOWN(arm64_dma_phys_limit);
> > >  #endif
> > >  #ifdef CONFIG_ZONE_DMA32
> > > diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c
> > > index ec782e4a0fe4..c3db44896e49 100644
> > > --- a/drivers/acpi/arm64/iort.c
> > > +++ b/drivers/acpi/arm64/iort.c
> > > @@ -1722,3 +1722,54 @@ void __init acpi_iort_init(void)
> > >
> > >       iort_init_platform_devices();
> > >  }
> > > +
> > > +#ifdef CONFIG_ZONE_DMA
> > > +/*
> > > + * Check the IORT whether any devices exist whose DMA mask is < 32 bits.
> > > + * If so, return the smallest value encountered, or 32 otherwise.
> > > + */
> > > +unsigned int __init acpi_iort_get_zone_dma_size(void)
> > > +{
> > > +     struct acpi_table_iort *iort;
> > > +     struct acpi_iort_node *node, *end;
> > > +     acpi_status status;
> > > +     u8 limit = 32;
> > > +     int i;
> > > +
> > > +     if (acpi_disabled)
> > > +             return limit;
> > > +
> > > +     status = acpi_get_table(ACPI_SIG_IORT, 0,
> > > +                             (struct acpi_table_header **)&iort);
> > > +     if (ACPI_FAILURE(status))
> > > +             return limit;
> > > +
> > > +     node = ACPI_ADD_PTR(struct acpi_iort_node, iort, iort->node_offset);
> > > +     end = ACPI_ADD_PTR(struct acpi_iort_node, iort, iort->header.length);
> > > +
> > > +     for (i = 0; i < iort->node_count; i++) {
> > > +             if (node >= end)
> > > +                     break;
> > > +
> > > +             switch (node->type) {
> > > +                     struct acpi_iort_named_component *ncomp;
> > > +                     struct acpi_iort_root_complex *rc;
> > > +
> > > +             case ACPI_IORT_NODE_NAMED_COMPONENT:
> > > +                     ncomp = (struct acpi_iort_named_component *)node->node_data;
> > > +                     if (ncomp->memory_address_limit)
> > > +                             limit = min(limit, ncomp->memory_address_limit);
> > > +                     break;
> > > +
> > > +             case ACPI_IORT_NODE_PCI_ROOT_COMPLEX:
> > > +                     rc = (struct acpi_iort_root_complex *)node->node_data;
> > > +                     if (rc->memory_address_limit);
> >
> > You need a node->revision check here otherwise we may end up
> > dereferencing junk. AKA ACPI versioning in all its glory.
> >
> 
> The address limit field was there since the beginning, and DEN0049B
> defines its value as 0x0, so I don't think we need to check anything
> here.
> 
> 
> > Thanks,
> > Lorenzo
> >
> > > +                             limit = min(limit, rc->memory_address_limit);
> > > +                     break;
> > > +             }
> > > +             node = ACPI_ADD_PTR(struct acpi_iort_node, node, node->length);
> > > +     }
> > > +     acpi_put_table(&iort->header);
> > > +     return limit;
> > > +}
> > > +#endif
> > > --
> > > 2.17.1
> > >

WARNING: multiple messages have this Message-ID (diff)
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Jeremy Linton <jeremy.linton@arm.com>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Hanjun Guo <guohanjun@huawei.com>, Will Deacon <will@kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Subject: Re: [PATCH] arm64: mm: set ZONE_DMA size based on early IORT scan
Date: Tue, 13 Oct 2020 14:13:46 +0100	[thread overview]
Message-ID: <20201013131346.GA20925@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <CAMj1kXEbZ3cN1N2V6MfbUZsTot+9TsLTC_UMm5JP1OW8AwvuOw@mail.gmail.com>

On Tue, Oct 13, 2020 at 01:22:32PM +0200, Ard Biesheuvel wrote:

[...]

> > > diff --git a/Documentation/arm64/arm-acpi.rst b/Documentation/arm64/arm-acpi.rst
> > > index 47ecb9930dde..947f5b5c45ef 100644
> > > --- a/Documentation/arm64/arm-acpi.rst
> > > +++ b/Documentation/arm64/arm-acpi.rst
> > > @@ -205,6 +205,13 @@ devices available.  This list of tables is not meant to be all inclusive;
> > >  in some environments other tables may be needed (e.g., any of the APEI
> > >  tables from section 18) to support specific functionality.
> > >
> > > +It is assumed that all DMA capable devices in the system are able to
> > > +access the lowest 4 GB of system memory. If this is not the case, an
> > > +IORT describing those limitations is mandatory, even if an IORT is not
> > > +otherwise necessary to describe the I/O topology, and regardless of
> > > +whether _DMA methods are used to describe the DMA limitations more
> > > +precisely. Once the system has booted, _DMA methods will take precedence
> > > +over DMA addressing limits described in the IORT.
> >
> > If this is a boot requirement it must be in ARM's official documentation,
> > first, not the kernel one.
> >
> > I understand this is an urgent (well - no comments on why bootstrapping
> > ACPI on Raspberry PI4 is causing all this fuss, honestly) fix but that's
> > not a reason to rush through these guidelines.
> >
> > I would not add this paragraph to arm-acpi.rst, yet.
> >
> 
> Which documentation? ACPI compliance by itself is not sufficient for a
> system to be able to boot Linux/arm64, which is why we documented the
> requirements for ACPI boot on Linux/arm64 in this file. I don't think
> we need endorsement from ARM to decide that odd platforms like this
> need to abide by some additional rules if they want to boot in ACPI
> mode.

I think we do - if we don't we should not add this documentation either.

ACPI on ARM64 software stack is based on standardized HW requirements.
The sheer fact that we need to work around a HW deficiency shows that
either this platform should have never been booted with ACPI or the _HW_
design guidelines (BSA) are not tight enough.

Please note that as you may have understood I asked if we can implement
a workaround in IORT because that's information that must be there
regardless (and an OEM ID match in arch code - though pragmatic -
defeats the whole purpose), I don't think we should tell Linux kernel
developers how firmware must be written to work around blatantly
non-compliant systems.

Thanks,
Lorenzo

> > >  ACPI Detection
> > >  --------------
> > > diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
> > > index f0599ae73b8d..829fa63c3d72 100644
> > > --- a/arch/arm64/mm/init.c
> > > +++ b/arch/arm64/mm/init.c
> > > @@ -191,6 +191,14 @@ static void __init zone_sizes_init(unsigned long min, unsigned long max)
> > >       unsigned long max_zone_pfns[MAX_NR_ZONES]  = {0};
> > >
> > >  #ifdef CONFIG_ZONE_DMA
> > > +     if (IS_ENABLED(CONFIG_ACPI)) {
> > > +             extern unsigned int acpi_iort_get_zone_dma_size(void);
> >
> > Yes as Catalin asked please add a declaration in IORT headers.
> >
> 
> Ack.
> 
> > > +             zone_dma_bits = min(zone_dma_bits,
> > > +                                 acpi_iort_get_zone_dma_size());
> > > +             arm64_dma_phys_limit = max_zone_phys(zone_dma_bits);
> > > +     }
> > > +
> > >       max_zone_pfns[ZONE_DMA] = PFN_DOWN(arm64_dma_phys_limit);
> > >  #endif
> > >  #ifdef CONFIG_ZONE_DMA32
> > > diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c
> > > index ec782e4a0fe4..c3db44896e49 100644
> > > --- a/drivers/acpi/arm64/iort.c
> > > +++ b/drivers/acpi/arm64/iort.c
> > > @@ -1722,3 +1722,54 @@ void __init acpi_iort_init(void)
> > >
> > >       iort_init_platform_devices();
> > >  }
> > > +
> > > +#ifdef CONFIG_ZONE_DMA
> > > +/*
> > > + * Check the IORT whether any devices exist whose DMA mask is < 32 bits.
> > > + * If so, return the smallest value encountered, or 32 otherwise.
> > > + */
> > > +unsigned int __init acpi_iort_get_zone_dma_size(void)
> > > +{
> > > +     struct acpi_table_iort *iort;
> > > +     struct acpi_iort_node *node, *end;
> > > +     acpi_status status;
> > > +     u8 limit = 32;
> > > +     int i;
> > > +
> > > +     if (acpi_disabled)
> > > +             return limit;
> > > +
> > > +     status = acpi_get_table(ACPI_SIG_IORT, 0,
> > > +                             (struct acpi_table_header **)&iort);
> > > +     if (ACPI_FAILURE(status))
> > > +             return limit;
> > > +
> > > +     node = ACPI_ADD_PTR(struct acpi_iort_node, iort, iort->node_offset);
> > > +     end = ACPI_ADD_PTR(struct acpi_iort_node, iort, iort->header.length);
> > > +
> > > +     for (i = 0; i < iort->node_count; i++) {
> > > +             if (node >= end)
> > > +                     break;
> > > +
> > > +             switch (node->type) {
> > > +                     struct acpi_iort_named_component *ncomp;
> > > +                     struct acpi_iort_root_complex *rc;
> > > +
> > > +             case ACPI_IORT_NODE_NAMED_COMPONENT:
> > > +                     ncomp = (struct acpi_iort_named_component *)node->node_data;
> > > +                     if (ncomp->memory_address_limit)
> > > +                             limit = min(limit, ncomp->memory_address_limit);
> > > +                     break;
> > > +
> > > +             case ACPI_IORT_NODE_PCI_ROOT_COMPLEX:
> > > +                     rc = (struct acpi_iort_root_complex *)node->node_data;
> > > +                     if (rc->memory_address_limit);
> >
> > You need a node->revision check here otherwise we may end up
> > dereferencing junk. AKA ACPI versioning in all its glory.
> >
> 
> The address limit field was there since the beginning, and DEN0049B
> defines its value as 0x0, so I don't think we need to check anything
> here.
> 
> 
> > Thanks,
> > Lorenzo
> >
> > > +                             limit = min(limit, rc->memory_address_limit);
> > > +                     break;
> > > +             }
> > > +             node = ACPI_ADD_PTR(struct acpi_iort_node, node, node->length);
> > > +     }
> > > +     acpi_put_table(&iort->header);
> > > +     return limit;
> > > +}
> > > +#endif
> > > --
> > > 2.17.1
> > >

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-10-13 13:13 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-10  9:31 [PATCH] arm64: mm: set ZONE_DMA size based on early IORT scan Ard Biesheuvel
2020-10-10  9:31 ` Ard Biesheuvel
2020-10-12  9:28 ` Catalin Marinas
2020-10-12  9:28   ` Catalin Marinas
2020-10-12  9:30   ` Ard Biesheuvel
2020-10-12  9:30     ` Ard Biesheuvel
2020-10-12 10:43     ` Ard Biesheuvel
2020-10-12 10:43       ` Ard Biesheuvel
2020-10-12 11:24       ` Catalin Marinas
2020-10-12 11:24         ` Catalin Marinas
2020-10-12 14:19         ` Ard Biesheuvel
2020-10-12 14:19           ` Ard Biesheuvel
2020-10-12 15:49           ` Catalin Marinas
2020-10-12 15:49             ` Catalin Marinas
2020-10-12 15:55             ` Ard Biesheuvel
2020-10-12 15:55               ` Ard Biesheuvel
2020-10-12 16:22               ` Catalin Marinas
2020-10-12 16:22                 ` Catalin Marinas
2020-10-12 16:35                 ` Ard Biesheuvel
2020-10-12 16:35                   ` Ard Biesheuvel
2020-10-12 16:59                   ` Catalin Marinas
2020-10-12 16:59                     ` Catalin Marinas
2020-10-13 14:42                     ` Nicolas Saenz Julienne
2020-10-13 14:42                       ` Nicolas Saenz Julienne
2020-10-13 15:45                       ` Catalin Marinas
2020-10-13 15:45                         ` Catalin Marinas
2020-10-14 12:44                       ` Ard Biesheuvel
2020-10-14 12:44                         ` Ard Biesheuvel
2020-10-14 12:54                         ` Nicolas Saenz Julienne
2020-10-14 12:54                           ` Nicolas Saenz Julienne
2020-10-12 12:16 ` kernel test robot
2020-10-12 12:16   ` kernel test robot
2020-10-12 12:16   ` kernel test robot
2020-10-13 11:09 ` Lorenzo Pieralisi
2020-10-13 11:09   ` Lorenzo Pieralisi
2020-10-13 11:22   ` Ard Biesheuvel
2020-10-13 11:22     ` Ard Biesheuvel
2020-10-13 11:38     ` Ard Biesheuvel
2020-10-13 11:38       ` Ard Biesheuvel
2020-10-13 11:43       ` Ard Biesheuvel
2020-10-13 11:43         ` Ard Biesheuvel
2020-10-13 13:13     ` Lorenzo Pieralisi [this message]
2020-10-13 13:13       ` Lorenzo Pieralisi
2020-10-13 13:42       ` Ard Biesheuvel
2020-10-13 13:42         ` Ard Biesheuvel
2020-10-13 15:11         ` Robin Murphy
2020-10-13 15:11           ` Robin Murphy
2020-10-13 15:41         ` Lorenzo Pieralisi
2020-10-13 15:41           ` Lorenzo Pieralisi
2020-10-14 16:18           ` Catalin Marinas
2020-10-14 16:18             ` Catalin Marinas
2020-10-14 17:23             ` Lorenzo Pieralisi
2020-10-14 17:23               ` Lorenzo Pieralisi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201013131346.GA20925@e121166-lin.cambridge.arm.com \
    --to=lorenzo.pieralisi@arm.com \
    --cc=anshuman.khandual@arm.com \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=guohanjun@huawei.com \
    --cc=hch@lst.de \
    --cc=jeremy.linton@arm.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=nsaenzjulienne@suse.de \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=sudeep.holla@arm.com \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.