From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/3] arm64: KVM: Enable Common Not Private translations
Date: Fri, 27 Jul 2018 13:02:44 +0100 [thread overview]
Message-ID: <72c743b4-cdc1-6645-22ca-0efcb1ca420a@arm.com> (raw)
In-Reply-To: <20180727114142.2llrh6gcotlvs6lk@armageddon.cambridge.arm.com>
On 27/07/18 12:41, Catalin Marinas wrote:
> On Tue, Jun 19, 2018 at 11:18:21AM +0100, Vladimir Murzin wrote:
>> We rely on cpufeature framework to detect and enable CNP so for KVM we
>> need to patch hyp to set CNP bit just before TTBR0_EL2 gets written.
>>
>> For the guest we encode CNP bit while building vttbr, so we don't need
>> to bother with that in a world switch.
>>
>> Reviewed-by: James Morse <james.morse@arm.com>
>> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>
>
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
>
> (but you should get an ack from the kvm maintainers)
This is absolutely fine by me:
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2018-07-27 12:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 10:18 [PATCH v5 0/3] Support Common Not Private translations Vladimir Murzin
2018-06-19 10:18 ` [PATCH v5 1/3] arm64: mm: " Vladimir Murzin
2018-07-27 11:35 ` Catalin Marinas
2018-07-30 10:08 ` Vladimir Murzin
2018-07-30 15:42 ` Catalin Marinas
2018-07-30 16:29 ` Robin Murphy
2018-07-30 17:03 ` Catalin Marinas
2018-07-31 10:17 ` Vladimir Murzin
2018-07-31 11:29 ` Catalin Marinas
2018-07-30 16:24 ` Suzuki K Poulose
2018-07-31 10:18 ` Vladimir Murzin
2018-06-19 10:18 ` [PATCH v5 2/3] arm64: KVM: Enable " Vladimir Murzin
2018-07-27 11:41 ` Catalin Marinas
2018-07-27 12:02 ` Marc Zyngier [this message]
2018-06-19 10:18 ` [PATCH v5 3/3] arm64: Introduce command line parameter to disable CNP Vladimir Murzin
2018-07-27 11:43 ` Catalin Marinas
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=72c743b4-cdc1-6645-22ca-0efcb1ca420a@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 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.