From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5] irqchip, gicv3-its, numa: Enable workaround for Cavium thunderx erratum 23144
Date: Fri, 22 Apr 2016 10:00:52 +0100 [thread overview]
Message-ID: <20160422090052.GA4236@arm.com> (raw)
In-Reply-To: <5719DA41.60304@arm.com>
On Fri, Apr 22, 2016 at 09:01:05AM +0100, Marc Zyngier wrote:
> On 21/04/16 18:40, Robert Richter wrote:
> > On 15.04.16 21:30:05, Robert Richter wrote:
> >> From: Ganapatrao Kulkarni <gkulkarni@caviumnetworks.com>
> >>
> >> The erratum fixes the hang of ITS SYNC command by avoiding inter node
> >> io and collections/cpu mapping on thunderx dual-socket platform.
> >>
> >> This fix is only applicable for Cavium's ThunderX dual-socket platform.
> >>
> >> This is based on NUMA v16 series.
> >> Message-Id: <1460155828-8690-1-git-send-email-ddaney.cavm@gmail.com>
> >
> > Will, Catalin,
> >
> > after NUMA base patches went into linux-next (many thanks), please
> > consider this pass 1.x errata workaround for inclusion too.
>
> I'll queue it as a fix once the NUMA patches are merged into mainline.
Yeah, this can probably go in as -rc1 material if you're happy with it.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Robert Richter <robert.richter@caviumnetworks.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
David Daney <david.daney@caviumnetworks.com>,
gpkulkarni@gmail.com,
Ganapatrao Kulkarni <gkulkarni@caviumnetworks.com>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] irqchip, gicv3-its, numa: Enable workaround for Cavium thunderx erratum 23144
Date: Fri, 22 Apr 2016 10:00:52 +0100 [thread overview]
Message-ID: <20160422090052.GA4236@arm.com> (raw)
In-Reply-To: <5719DA41.60304@arm.com>
On Fri, Apr 22, 2016 at 09:01:05AM +0100, Marc Zyngier wrote:
> On 21/04/16 18:40, Robert Richter wrote:
> > On 15.04.16 21:30:05, Robert Richter wrote:
> >> From: Ganapatrao Kulkarni <gkulkarni@caviumnetworks.com>
> >>
> >> The erratum fixes the hang of ITS SYNC command by avoiding inter node
> >> io and collections/cpu mapping on thunderx dual-socket platform.
> >>
> >> This fix is only applicable for Cavium's ThunderX dual-socket platform.
> >>
> >> This is based on NUMA v16 series.
> >> Message-Id: <1460155828-8690-1-git-send-email-ddaney.cavm@gmail.com>
> >
> > Will, Catalin,
> >
> > after NUMA base patches went into linux-next (many thanks), please
> > consider this pass 1.x errata workaround for inclusion too.
>
> I'll queue it as a fix once the NUMA patches are merged into mainline.
Yeah, this can probably go in as -rc1 material if you're happy with it.
Will
next prev parent reply other threads:[~2016-04-22 9:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 19:30 [PATCH v5] irqchip, gicv3-its, numa: Enable workaround for Cavium thunderx erratum 23144 Robert Richter
2016-04-15 19:30 ` Robert Richter
2016-04-21 17:40 ` Robert Richter
2016-04-21 17:40 ` Robert Richter
2016-04-22 8:01 ` Marc Zyngier
2016-04-22 8:01 ` Marc Zyngier
2016-04-22 9:00 ` Will Deacon [this message]
2016-04-22 9:00 ` Will Deacon
2016-05-25 13:22 ` Robert Richter
2016-05-25 13:22 ` 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=20160422090052.GA4236@arm.com \
--to=will.deacon@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 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.