From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: KVM: Obey RES0/1 reserved bits when setting CPTR_EL2
Date: Tue, 19 Jan 2016 16:32:43 +0000 [thread overview]
Message-ID: <569E652B.8040202@arm.com> (raw)
In-Reply-To: <1453220418-24744-1-git-send-email-Dave.Martin@arm.com>
On 19/01/16 16:20, Dave Martin wrote:
> Some bits in CPTR are defined as RES1 in the architecture. Setting
> these bits to zero may unintentionally enable future architecture
> extensions, allowing guests to use them without supervision by the host.
>
> This would be bad: for forwards compatibility, this patch makes
> sure the affected bits are always written with 1, not 0.
>
> This patch only addresses CPTR_EL2. Initialisation of other system
> registers may still need review.
>
> Signed-off-by: Dave Martin <Dave.Martin@arm.com>
Thanks for putting this together:
Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
Unless someone has an objection, I plan to queue this post -rc1.
M.
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2016-01-19 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 16:20 [PATCH] arm64: KVM: Obey RES0/1 reserved bits when setting CPTR_EL2 Dave Martin
2016-01-19 16:32 ` Marc Zyngier [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=569E652B.8040202@arm.com \
--to=marc.zyngier@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 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).