From: Marc Zyngier <maz@kernel.org>
To: Lorenzo Pieralisi <lpieralisi@kernel.org>
Cc: linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org,
acpica-devel@lists.linux.dev, Fang Xiang <fangxiang3@xiaomi.com>,
Robert Moore <robert.moore@intel.com>
Subject: Re: [PATCH v5 1/1] irqchip/gic-v3: Enable non-coherent redistributors/ITSes ACPI probing
Date: Wed, 05 Jun 2024 09:40:34 +0100 [thread overview]
Message-ID: <eefc3a76d6cfb3400a3d6e39e8887177@kernel.org> (raw)
In-Reply-To: <ZmAQQVR+inUJpJ7z@lpieralisi>
On 2024-06-05 08:14, Lorenzo Pieralisi wrote:
> On Mon, Apr 22, 2024 at 10:42:19AM +0200, Lorenzo Pieralisi wrote:
>> On Tue, Jan 23, 2024 at 12:03:32PM +0100, Lorenzo Pieralisi wrote:
>> > The GIC architecture specification defines a set of registers for
>> > redistributors and ITSes that control the sharebility and cacheability
>> > attributes of redistributors/ITSes initiator ports on the interconnect
>> > (GICR_[V]PROPBASER, GICR_[V]PENDBASER, GITS_BASER<n>).
>> >
>> > Architecturally the GIC provides a means to drive shareability and
>> > cacheability attributes signals but it is not mandatory for designs to
>> > wire up the corresponding interconnect signals that control the
>> > cacheability/shareability of transactions.
>> >
>> > Redistributors and ITSes interconnect ports can be connected to
>> > non-coherent interconnects that are not able to manage the
>> > shareability/cacheability attributes; this implicitly makes the
>> > redistributors and ITSes non-coherent observers.
>> >
>> > To enable non-coherent GIC designs on ACPI based systems, parse the MADT
>> > GICC/GICR/ITS subtables non-coherent flags to determine whether the
>> > respective components are non-coherent observers and force the
>> > shareability attributes to be programmed into the redistributors and
>> > ITSes registers.
>> >
>> > An ACPI global function (acpi_get_madt_revision()) is added to retrieve
>> > the MADT revision, in that it is essential to check the MADT revision
>> > before checking for flags that were added with MADT revision 7 so that
>> > if the kernel is booted with an ACPI MADT table with revision < 7 it
>> > skips parsing the newly added flags (that should be zeroed reserved
>> > values for MADT versions < 7 but they could turn out to be buggy and
>> > should be ignored).
>> >
>> > Signed-off-by: Lorenzo Pieralisi <lpieralisi@kernel.org>
>> > Cc: Robin Murphy <robin.murphy@arm.com>
>> > Cc: Mark Rutland <mark.rutland@arm.com>
>> > Cc: "Rafael J. Wysocki" <rafael@kernel.org>
>> > Cc: Marc Zyngier <maz@kernel.org>
>> > ---
>> > drivers/acpi/processor_core.c | 15 +++++++++++++++
>> > drivers/irqchip/irq-gic-v3-its.c | 4 ++++
>> > drivers/irqchip/irq-gic-v3.c | 9 +++++++++
>> > include/linux/acpi.h | 3 +++
>> > 4 files changed, 31 insertions(+)
>>
>> Hi Marc, Rafael,
>>
>> I would kindly ask you please what to do with this patch, it still
>> applies to v6.9-rc5 - I can resend it if needed, ACPICA changes
>> are already merged as-per the cover letter.
>
> Hi Marc, Rafael,
>
> I would kindly ask please what to do with this patch, rebased to
> v6.10-rc1,
> I can resend it if that's preferred, please let me know.
Please resend it with my:
Acked-by: Marc Zyngier <maz@kernel.org>
and Cc'ing Thomas Gleixner.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-06-05 8:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 11:03 [PATCH v5 0/1] irqchip/gic-v3: Enable non-coherent GIC designs probing Lorenzo Pieralisi
2024-01-23 11:03 ` [PATCH v5 1/1] irqchip/gic-v3: Enable non-coherent redistributors/ITSes ACPI probing Lorenzo Pieralisi
2024-01-23 13:36 ` Robin Murphy
2024-04-22 8:42 ` Lorenzo Pieralisi
2024-06-05 7:14 ` Lorenzo Pieralisi
2024-06-05 8:40 ` Marc Zyngier [this message]
2024-03-06 14:43 ` [PATCH v5 0/1] irqchip/gic-v3: Enable non-coherent GIC designs probing Lorenzo Pieralisi
2024-04-08 14:54 ` Lorenzo Pieralisi
2024-06-06 9:42 ` [PATCH v6 " Lorenzo Pieralisi
2024-06-06 9:42 ` [PATCH v6 1/1] irqchip/gic-v3: Enable non-coherent redistributors/ITSes ACPI probing Lorenzo Pieralisi
2024-06-06 18:51 ` Amit Singh Tomar
2024-06-07 7:39 ` Lorenzo Pieralisi
2024-06-07 7:53 ` Amit Singh Tomar
2024-06-07 9:10 ` Robin Murphy
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=eefc3a76d6cfb3400a3d6e39e8887177@kernel.org \
--to=maz@kernel.org \
--cc=acpica-devel@lists.linux.dev \
--cc=fangxiang3@xiaomi.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=robin.murphy@arm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).