From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/6] irqchip, gicv3: Updates and Cavium ThunderX errata workarounds
Date: Tue, 22 Sep 2015 20:41:34 +0100 [thread overview]
Message-ID: <20150922204134.7491db93@arm.com> (raw)
In-Reply-To: <20150922182726.GN7356@arm.com>
On Tue, 22 Sep 2015 19:27:26 +0100
Will Deacon <will.deacon@arm.com> wrote:
> On Tue, Sep 22, 2015 at 07:09:32PM +0100, Marc Zyngier wrote:
> > On Tue, 22 Sep 2015 17:57:01 +0100
> > Marc Zyngier <marc.zyngier@arm.com> wrote:
> >
> > [Duh. Now with Will and Catalin on CC]
> >
> > > On Mon, 21 Sep 2015 22:58:33 +0200
> > > Robert Richter <rric@kernel.org> wrote:
> > >
> > > > From: Robert Richter <rrichter@cavium.com>
> > > >
> > > > This patch series adds gicv3 updates and workarounds for HW errata in
> > > > Cavium's ThunderX GICV3.
> > > >
> > > > The patches has been rebased onto 4.3-rc1. Note that there are two
> > > > important fixes. See below for all changes.
> > > >
> > > > The first one is an unchanged resubmission of a patch from a gicv3
> > > > series I sent a while ago.
> > > >
> > > > The next patches implement the workarounds for ThunderX's gicv3. Patch
> > > > #2 implements the cpu workaround for gicv3 on ThunderX. Patch #3 is a
> > > > prerequisit for patch #5. Patch #4 adds generic code to parse the hw
> > > > revision provided by an IIDR. This patch is used for the implementa-
> > > > tion of the actual gicv3-its workaround in #5. Patch #6 updates to the
> > > > new jump label API.
> > > >
> > > > All current review comments addressed so far with v5
> > >
> > > Catalin, Will: assuming you don't have any objection to this series,
> > > how do you want to deal with patch 2?
>
> What are the actual dependencies here? AFAICT, the series is addressing
> multiple errata, so would it be possible to make the arm64 bits somewhat
> independent from the gic parts?
Patch 2 could be split into an arm64-specific part and a gic part, with
a bit of #ifdef-ery in gicv3_enable_quirks().
> Also, I assume this is targetting 4.4?
Up to you, really. It is not a regression, but it would still be nice
to have 4.3 working reliably on this HW.
Thanks,
M.
--
Jazz is not dead. It just smells funny.
next prev parent reply other threads:[~2015-09-22 19:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 20:58 [PATCH v5 0/6] irqchip, gicv3: Updates and Cavium ThunderX errata workarounds Robert Richter
2015-09-21 20:58 ` [PATCH v5 1/6] irqchip, gicv3-its: Add range check for number of allocated pages Robert Richter
2015-09-21 20:58 ` [PATCH v5 2/6] irqchip, gicv3: Workaround for Cavium ThunderX erratum 23154 Robert Richter
2015-09-22 16:50 ` Marc Zyngier
2015-09-21 20:58 ` [PATCH v5 3/6] irqchip, gicv3-its: Read typer register outside the loop Robert Richter
2015-09-21 20:58 ` [PATCH v5 4/6] irqchip, gicv3-its: Add HW revision detection and configuration Robert Richter
2015-09-22 16:51 ` Marc Zyngier
2015-09-21 20:58 ` [PATCH v5 5/6] irqchip, gicv3-its: Workaround for Cavium ThunderX errata 22375, 24313 Robert Richter
2015-09-22 16:52 ` Marc Zyngier
2015-09-21 20:58 ` [PATCH v5 6/6] irqchip, gicv3-its: Use new jump label API Robert Richter
2015-09-22 16:53 ` Marc Zyngier
2015-09-22 16:57 ` [PATCH v5 0/6] irqchip, gicv3: Updates and Cavium ThunderX errata workarounds Marc Zyngier
2015-09-22 18:09 ` Marc Zyngier
2015-09-22 18:27 ` Will Deacon
2015-09-22 19:41 ` Marc Zyngier [this message]
2015-09-24 16:54 ` Catalin Marinas
2015-09-24 17:01 ` Robert Richter
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=20150922204134.7491db93@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 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).