Re: [PATCH v3] arm64: Add workaround for Cavium erratum 27456

From	Will Deacon <will.deacon@arm.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH v3] arm64: Add workaround for Cavium erratum 27456
Date	2016-02-24 19:10 +0100
Message-ID	<r5M2S-8jZ-11@gated-at.bofh.it> (permalink)
References	<r5vbJ-4KX-5@gated-at.bofh.it> <r5HZf-5i2-9@gated-at.bofh.it> <r5IiE-5Ha-19@gated-at.bofh.it> <r5M2T-8jZ-13@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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

Thread

[PATCH v3] arm64: Add workaround for Cavium erratum 27456 David Daney <ddaney.cavm@gmail.com> - 2016-02-24 01:10 +0100
  Re: [PATCH v3] arm64: Add workaround for Cavium erratum 27456 Will Deacon <will.deacon@arm.com> - 2016-02-24 14:50 +0100
    Re: [PATCH v3] arm64: Add workaround for Cavium erratum 27456 Marc Zyngier <marc.zyngier@arm.com> - 2016-02-24 15:10 +0100
      Re: [PATCH v3] arm64: Add workaround for Cavium erratum 27456 Will Deacon <will.deacon@arm.com> - 2016-02-24 19:10 +0100
        Re: [PATCH v3] arm64: Add workaround for Cavium erratum 27456 David Daney <ddaney@caviumnetworks.com> - 2016-02-24 19:10 +0100
      Re: [PATCH v3] arm64: Add workaround for Cavium erratum 27456 David Daney <ddaney@caviumnetworks.com> - 2016-02-24 19:10 +0100

csiph-web