Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Marc Zyngier <maz@kernel.org>
To:     Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
        Sudeep Holla <sudeep.holla@arm.com>,
        Hanjun Guo <guohanjun@huawei.com>
Cc:     dann frazier <dann.frazier@canonical.com>,
        Fu Wei <wefu@redhat.com>, Len Brown <lenb@kernel.org>,
        "Rafael J. Wysocki" <rjw@rjwysocki.net>,
        linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [PATCH 0/2] arm64: ACPI GTDT watchdog fixes
Date:   Wed, 21 Apr 2021 17:43:15 +0100
Message-Id: <20210421164317.1718831-1-maz@kernel.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Dann recently reported that his ThunderX machine failed to boot since
64b499d8df40 ("irqchip/gic-v3: Configure SGIs as standard
interrupts"), with a not so pretty crash while trying to send an IPI.

It turned out to be caused by a mix of broken firmware and a buggy
GTDT watchdog driver. Both have forever been buggy, but the above
commit revealed that the error handling path of the driver was
probably the worse part of it all.

Anyway, this short series has two goals:
- handle broken firmware in a less broken way
- make sure that the route cause of the problem can be identified
  quickly

Thanks,

	M.

Marc Zyngier (2):
  ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure
  ACPI: irq: Prevent unregistering of GIC SGIs

 drivers/acpi/arm64/gtdt.c | 10 ++++++----
 drivers/acpi/irq.c        |  6 +++++-
 2 files changed, 11 insertions(+), 5 deletions(-)

-- 
2.29.2