From: Sasha Levin <sashal@kernel.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: will@kernel.org, gregkh@linuxfoundation.org, stable@vger.kernel.org
Subject: Re: [PATCH 0/2] [Backport for 4.4.y stable] arm64 CTR_EL0 cpufeature fixes
Date: Wed, 7 Aug 2019 08:53:03 -0400 [thread overview]
Message-ID: <20190807125303.GT17747@sasha-vm> (raw)
In-Reply-To: <e5628f61-5839-675b-6826-ca37d00ce24a@arm.com>
On Wed, Aug 07, 2019 at 11:59:41AM +0100, Suzuki K Poulose wrote:
>Hi Will,
>
>On 07/08/2019 10:49, Will Deacon wrote:
>>Hi Sasha, [+Suzuki]
>>
>>On Tue, Aug 06, 2019 at 05:29:04PM -0400, Sasha Levin wrote:
>>>On Mon, Aug 05, 2019 at 06:13:06PM +0100, Will Deacon wrote:
>>>>These two patches are backports for 4.4.y stable kernels after one of
>>>>them failed to apply:
>>>>
>>>> https://lkml.kernel.org/r/156498316752100@kroah.com
>>>
>>>I took these 2, but note that they have two fixes that are not in 4.4:
>>>
>>>314d53d297980 arm64: Handle mismatched cache type
>>>4c4a39dd5fe2d arm64: Fix mismatched cache line size detection
>>>
>>>Will you send a backport for them?
>>
>>4.4 doesn't handle mismatches for the cache type or the line sizes, and
>>instead taints the kernel with a big splat at boot. If we wanted to
>>backport this, we'd need to pick up more than just the above patches, since
>>we don't have the means to emulate user cache maintenance operations either.
>>
>>Given that the vast majority of systems don't suffer from this problem,
>>I'd be inclined not to try shoe-horning all of this into 4.4, where I think
>>it's more likely introduce other issues.
>>
>>Suzuki, what do you think?
>
>I agree. It involves a lot of new code, with non-trivial backports.
Okay, makes sense. Thanks for looking into it.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-08-07 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 17:13 [PATCH 0/2] [Backport for 4.4.y stable] arm64 CTR_EL0 cpufeature fixes Will Deacon
2019-08-05 17:13 ` [PATCH 1/2] arm64: cpufeature: Fix CTR_EL0 field definitions Will Deacon
2019-08-05 17:13 ` [PATCH 2/2] arm64: cpufeature: Fix feature comparison for CTR_EL0.{CWG,ERG} Will Deacon
2019-08-06 21:29 ` [PATCH 0/2] [Backport for 4.4.y stable] arm64 CTR_EL0 cpufeature fixes Sasha Levin
2019-08-07 9:49 ` Will Deacon
2019-08-07 10:59 ` Suzuki K Poulose
2019-08-07 12:53 ` Sasha Levin [this message]
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=20190807125303.GT17747@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.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.