From: Suzuki Kuruppassery Poulose <suzuki.poulose@arm.com>
To: Andrew Murray <andrew.murray@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/3] arm64: cpufeature: Extract capped fields
Date: Thu, 2 Jan 2020 16:22:26 +0000 [thread overview]
Message-ID: <cbf5e5e0-a31a-3f52-c113-7e069c920bf1@arm.com> (raw)
In-Reply-To: <20200102123905.29360-2-andrew.murray@arm.com>
On 02/01/2020 12:39, Andrew Murray wrote:
> When emulating ID registers there is often a need to cap the version
> bits of a feature such that the guest will not use features that do
> not yet exist.
>
> Let's add a helper that extracts a field and caps the version to a
> given value.
>
> Signed-off-by: Andrew Murray <andrew.murray@arm.com>
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2020-01-02 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 12:39 [PATCH v3 0/3] arm64: perf: Add support for ARMv8.5-PMU 64-bit counters Andrew Murray
2020-01-02 12:39 ` [PATCH v3 1/3] arm64: cpufeature: Extract capped fields Andrew Murray
2020-01-02 16:22 ` Suzuki Kuruppassery Poulose [this message]
2020-01-02 12:39 ` [PATCH v3 2/3] KVM: arm64: limit PMU version to ARMv8.4 Andrew Murray
2020-01-20 17:44 ` Will Deacon
2020-01-21 11:28 ` Andrew Murray
2020-01-20 17:55 ` Marc Zyngier
2020-01-21 9:04 ` Will Deacon
2020-01-21 11:18 ` Andrew Murray
2020-01-21 11:24 ` Andrew Murray
2020-01-02 12:39 ` [PATCH v3 3/3] arm64: perf: Add support for ARMv8.5-PMU 64-bit counters Andrew Murray
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=cbf5e5e0-a31a-3f52-c113-7e069c920bf1@arm.com \
--to=suzuki.poulose@arm.com \
--cc=andrew.murray@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--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 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).