From: Catalin Marinas <catalin.marinas@arm.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
pelcan@codeaurora.org, will.deacon@arm.com,
linux-kernel@vger.kernel.org, shankerd@codeaurora.org
Subject: Re: [PATCH v2 0/3] arm64: cpufeature: Fix handling of CTR_EL0
Date: Tue, 16 Oct 2018 12:00:26 +0100 [thread overview]
Message-ID: <20181016110005.GF108539@arrakis.emea.arm.com> (raw)
In-Reply-To: <20181009134707.3479-1-suzuki.poulose@arm.com>
On Tue, Oct 09, 2018 at 02:47:03PM +0100, Suzuki K. Poulose wrote:
> This series makes sure that we handle the CTR_EL0 field mismatches
> properly, especially for the IDC field. Also, skip trapping CTR
> accesses on a CPU if it matches the safe value.
>
> Applies on arm64 for-next/core.
>
> Changes since v1
> - Fix wrong hunk in has_cache_idc()
> - Allow a late secondary CPU with raw CTR_EL0.IDC = 0 and effective
> CTR_EL0.IDC = 1, to boot on a system without IDC available.
>
> Suzuki K Poulose (3):
> arm64: cpufeature: ctr: Fix cpu capability check for late CPUs
> arm64: cpufeature: Fix handling of CTR_EL0.IDC field
> arm64: cpufeature: Trap CTR_EL0 access only where it is necessary
Queued for 4.20. Thanks.
--
Catalin
prev parent reply other threads:[~2018-10-16 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 13:47 [PATCH v2 0/3] arm64: cpufeature: Fix handling of CTR_EL0 Suzuki K Poulose
2018-10-09 13:47 ` Suzuki K Poulose
2018-10-09 13:47 ` [PATCH v2 1/3] arm64: cpufeature: ctr: Fix cpu capability check for late CPUs Suzuki K Poulose
2018-10-09 13:47 ` [PATCH v2 2/3] arm64: cpufeature: Fix handling of CTR_EL0.IDC field Suzuki K Poulose
2018-10-09 13:47 ` [PATCH v2 3/3] arm64: cpufeature: Trap CTR_EL0 access only where it is necessary Suzuki K Poulose
2018-10-16 11:00 ` Catalin Marinas [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=20181016110005.GF108539@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pelcan@codeaurora.org \
--cc=shankerd@codeaurora.org \
--cc=suzuki.poulose@arm.com \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).