From: David Daney <ddaney@caviumnetworks.com>
To: Robert Richter <robert.richter@cavium.com>
Cc: mark.rutland@arm.com, Matthias Brugger <mbrugger@suse.com>,
christoffer.dall@linaro.org, david.daney@cavium.com,
kvm@vger.kernel.org, suzuki.poulose@arm.com,
marc.zyngier@arm.com, catalin.marinas@arm.com,
rkrcmar@redhat.com, will.deacon@arm.com, linux@armlinux.org.uk,
agraf@suse.de, ard.biesheuvel@linaro.org,
lorenzo.pieralisi@arm.com, james.morse@arm.com,
dave.long@linaro.org, zlim.lnx@gmail.com, pbonzini@redhat.com,
kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: Add workaround for Cavium erratum 26026
Date: Fri, 5 Aug 2016 09:37:39 -0700 [thread overview]
Message-ID: <57A4C0D3.2060408@caviumnetworks.com> (raw)
In-Reply-To: <20160805070030.GQ22012@rric.localdomain>
On 08/05/2016 12:00 AM, Robert Richter wrote:
> On 04.08.16 14:40:48, David Daney wrote:
>> On 08/04/2016 01:57 PM, Robert Richter wrote:
>>> The patch below is on top of Matthias' patch series:
>>>
>>> arm64: Implement IPI based TLB invalidation
>>>
>>> The series is used to enable a workaround for Cavium ThunderX pass 1.x
>>> systems.
>>
>>
>> Where are the rest of the patches in the series? I would have expected
>> something like "[PATCH 1/X] arm64:..." with X being greater than one.
>
> You are cc'ed here too:
>
> https://lkml.org/lkml/2016/8/4/101
>
OK, I got confused by the fact that this patch was retroactively added
to the patch set and was missing the sequence numbering.
> -Robert
>
WARNING: multiple messages have this Message-ID (diff)
From: ddaney@caviumnetworks.com (David Daney)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Add workaround for Cavium erratum 26026
Date: Fri, 5 Aug 2016 09:37:39 -0700 [thread overview]
Message-ID: <57A4C0D3.2060408@caviumnetworks.com> (raw)
In-Reply-To: <20160805070030.GQ22012@rric.localdomain>
On 08/05/2016 12:00 AM, Robert Richter wrote:
> On 04.08.16 14:40:48, David Daney wrote:
>> On 08/04/2016 01:57 PM, Robert Richter wrote:
>>> The patch below is on top of Matthias' patch series:
>>>
>>> arm64: Implement IPI based TLB invalidation
>>>
>>> The series is used to enable a workaround for Cavium ThunderX pass 1.x
>>> systems.
>>
>>
>> Where are the rest of the patches in the series? I would have expected
>> something like "[PATCH 1/X] arm64:..." with X being greater than one.
>
> You are cc'ed here too:
>
> https://lkml.org/lkml/2016/8/4/101
>
OK, I got confused by the fact that this patch was retroactively added
to the patch set and was missing the sequence numbering.
> -Robert
>
WARNING: multiple messages have this Message-ID (diff)
From: David Daney <ddaney@caviumnetworks.com>
To: Robert Richter <robert.richter@cavium.com>
Cc: <marc.zyngier@arm.com>, <linux@armlinux.org.uk>,
<catalin.marinas@arm.com>, <will.deacon@arm.com>,
<mark.rutland@arm.com>, Matthias Brugger <mbrugger@suse.com>,
<kvm@vger.kernel.org>, <suzuki.poulose@arm.com>,
<zlim.lnx@gmail.com>, <rkrcmar@redhat.com>,
<david.daney@cavium.com>, <agraf@suse.de>,
<linux-kernel@vger.kernel.org>, <ard.biesheuvel@linaro.org>,
<lorenzo.pieralisi@arm.com>, <james.morse@arm.com>,
<dave.long@linaro.org>, <pbonzini@redhat.com>,
<kvmarm@lists.cs.columbia.edu>, <christoffer.dall@linaro.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: Add workaround for Cavium erratum 26026
Date: Fri, 5 Aug 2016 09:37:39 -0700 [thread overview]
Message-ID: <57A4C0D3.2060408@caviumnetworks.com> (raw)
In-Reply-To: <20160805070030.GQ22012@rric.localdomain>
On 08/05/2016 12:00 AM, Robert Richter wrote:
> On 04.08.16 14:40:48, David Daney wrote:
>> On 08/04/2016 01:57 PM, Robert Richter wrote:
>>> The patch below is on top of Matthias' patch series:
>>>
>>> arm64: Implement IPI based TLB invalidation
>>>
>>> The series is used to enable a workaround for Cavium ThunderX pass 1.x
>>> systems.
>>
>>
>> Where are the rest of the patches in the series? I would have expected
>> something like "[PATCH 1/X] arm64:..." with X being greater than one.
>
> You are cc'ed here too:
>
> https://lkml.org/lkml/2016/8/4/101
>
OK, I got confused by the fact that this patch was retroactively added
to the patch set and was missing the sequence numbering.
> -Robert
>
next prev parent reply other threads:[~2016-08-05 16:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 9:15 arm64: Implement IPI based TLB invalidation Matthias Brugger
2016-08-04 9:15 ` Matthias Brugger
2016-08-04 9:15 ` [PATCH 1/4] arm64: insn: Do not disable irqs during patching Matthias Brugger
2016-08-04 9:15 ` Matthias Brugger
2016-08-04 9:15 ` [PATCH 2/4] arm64: Implement IPI based TLB invalidation Matthias Brugger
2016-08-04 9:15 ` Matthias Brugger
2016-08-04 9:15 ` [PATCH 3/4] KVM: arm/arm64: Check for broadcast TLBI support Matthias Brugger
2016-08-04 9:15 ` Matthias Brugger
2016-08-06 7:22 ` kbuild test robot
2016-08-06 7:22 ` kbuild test robot
2016-08-06 7:22 ` kbuild test robot
2016-08-06 7:22 ` kbuild test robot
2016-08-04 9:15 ` [PATCH 4/4] arm64: hibernate: " Matthias Brugger
2016-08-04 9:15 ` Matthias Brugger
2016-08-04 20:57 ` [PATCH] arm64: Add workaround for Cavium erratum 26026 Robert Richter
2016-08-04 20:57 ` Robert Richter
2016-08-04 20:57 ` Robert Richter
2016-08-04 20:57 ` Robert Richter
2016-08-04 21:40 ` David Daney
2016-08-04 21:40 ` David Daney
2016-08-05 7:00 ` Robert Richter
2016-08-05 7:00 ` Robert Richter
2016-08-05 7:00 ` Robert Richter
2016-08-05 16:37 ` David Daney [this message]
2016-08-05 16:37 ` David Daney
2016-08-05 16:37 ` David Daney
2016-08-05 2:35 ` kbuild test robot
2016-08-05 2:35 ` kbuild test robot
2016-08-05 2:35 ` kbuild test robot
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=57A4C0D3.2060408@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=agraf@suse.de \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=dave.long@linaro.org \
--cc=david.daney@cavium.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lorenzo.pieralisi@arm.com \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=mbrugger@suse.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=robert.richter@cavium.com \
--cc=suzuki.poulose@arm.com \
--cc=will.deacon@arm.com \
--cc=zlim.lnx@gmail.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 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.