From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] arm64: Add workaround for Cavium erratum 27456
Date: Wed, 24 Feb 2016 18:06:26 +0000 [thread overview]
Message-ID: <20160224180626.GF12471@arm.com> (raw)
In-Reply-To: <56CDF056.8020408@caviumnetworks.com>
On Wed, Feb 24, 2016 at 10:03:02AM -0800, David Daney wrote:
> On 02/24/2016 06:07 AM, Marc Zyngier wrote:
> >On 24/02/16 13:40, Will Deacon wrote:
> >
> >[...]
> >
> >>(and Catalin, if you pick this up, watch out for the conflicts in
> >>cpufeature.h)
> >
> >Yup, that one is about to become a minefield (ARM64_HAS_NO_HW_PREFETCH,
> >ARM64_HAS_UAO, ARM64_ALT_PAN_NOT_UAO and ARM64_HAS_VIRT_HOST_EXTN are
> >already happily clashing into -next). But hey, the more the merrier! ;-)
> >
>
> Would you like me to rebase it to for-next/core ?
I think ARM64_HAS_VIRT_HOST_EXTN is in the KVM tree, so you're probably
best off looking at linux-next and choosing your feature number based on
that, whilst basing the patch on either for-next/core or mainline.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
David Daney <ddaney.cavm@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org, Andrew Pinski <apinski@cavium.com>,
David Daney <david.daney@cavium.com>
Subject: Re: [PATCH v3] arm64: Add workaround for Cavium erratum 27456
Date: Wed, 24 Feb 2016 18:06:26 +0000 [thread overview]
Message-ID: <20160224180626.GF12471@arm.com> (raw)
In-Reply-To: <56CDF056.8020408@caviumnetworks.com>
On Wed, Feb 24, 2016 at 10:03:02AM -0800, David Daney wrote:
> On 02/24/2016 06:07 AM, Marc Zyngier wrote:
> >On 24/02/16 13:40, Will Deacon wrote:
> >
> >[...]
> >
> >>(and Catalin, if you pick this up, watch out for the conflicts in
> >>cpufeature.h)
> >
> >Yup, that one is about to become a minefield (ARM64_HAS_NO_HW_PREFETCH,
> >ARM64_HAS_UAO, ARM64_ALT_PAN_NOT_UAO and ARM64_HAS_VIRT_HOST_EXTN are
> >already happily clashing into -next). But hey, the more the merrier! ;-)
> >
>
> Would you like me to rebase it to for-next/core ?
I think ARM64_HAS_VIRT_HOST_EXTN is in the KVM tree, so you're probably
best off looking at linux-next and choosing your feature number based on
that, whilst basing the patch on either for-next/core or mainline.
Will
next prev parent reply other threads:[~2016-02-24 18:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 0:08 [PATCH v3] arm64: Add workaround for Cavium erratum 27456 David Daney
2016-02-24 0:08 ` David Daney
2016-02-24 13:40 ` Will Deacon
2016-02-24 13:40 ` Will Deacon
2016-02-24 14:07 ` Marc Zyngier
2016-02-24 14:07 ` Marc Zyngier
2016-02-24 18:03 ` David Daney
2016-02-24 18:03 ` David Daney
2016-02-24 18:06 ` Will Deacon [this message]
2016-02-24 18:06 ` Will Deacon
2016-02-24 18:07 ` David Daney
2016-02-24 18:07 ` David Daney
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=20160224180626.GF12471@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.