All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Tangnianyao <tangnianyao@huawei.com>
Cc: <kvmarm@lists.linux.dev>, <kvm@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	James Morse <james.morse@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Oliver Upton <oliver.upton@linux.dev>,
	Zenghui Yu <yuzenghui@huawei.com>,
	Quentin Perret <qperret@google.com>,
	Will Deacon <will@kernel.org>, Fuad Tabba <tabba@google.com>,
	"guoyang (C)" <guoyang2@huawei.com>
Subject: Re: [PATCH v3 00/17] KVM: arm64: Allow using VHE in the nVHE hypervisor
Date: Wed, 10 Jul 2024 09:51:24 +0100	[thread overview]
Message-ID: <86zfqp3a0j.wl-maz@kernel.org> (raw)
In-Reply-To: <5ab07210-ad44-616c-cd15-0ac954453fcf@huawei.com>

On Wed, 10 Jul 2024 07:45:52 +0100,
Tangnianyao <tangnianyao@huawei.com> wrote:
> 
> Hi Marz,
> 
> I'm trying to learn pKVM and have a question.
> 
> Why pKVM developed on E2H=0 firstly? It tried to avoid host access
> guest memory with stage2 translation, and it seems not necessarily
> rely on HCR_EL2.E2H=0.

Because we don't want to leave ARMv8.0 systems behind. They are still
a large portion of the arm64 HW running Linux.

> Is hVHE an alternative plan of pKVM ? To allow pKVM run on E2H res1 system ?

Supporting E2H RES1 implementations is indeed one of the motivations.
But there is a lot more to it, such as being able to use the two TTBRs
to perform address space isolation inside the hypervisor.

I presented this[1] at KVM Forum two years ago, which explains what we
could do (some of which is already in progress).

	M.

[1] https://static.sched.com/hosted_files/kvmforum2022/b4/NYSM-NYD-KVM-2022.pdf

-- 
Without deviation from the norm, progress is not possible.

      reply	other threads:[~2024-07-10  8:51 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09 16:21 [PATCH v3 00/17] KVM: arm64: Allow using VHE in the nVHE hypervisor Marc Zyngier
2023-06-09 16:21 ` Marc Zyngier
2023-06-09 16:21 ` [PATCH v3 01/17] KVM: arm64: Drop is_kernel_in_hyp_mode() from __invalidate_icache_guest_page() Marc Zyngier
2023-06-09 16:21   ` Marc Zyngier
2023-06-13  8:20   ` Shaoqin Huang
2023-06-09 16:21 ` [PATCH v3 02/17] arm64: Prevent the use of is_kernel_in_hyp_mode() in hypervisor code Marc Zyngier
2023-06-09 16:21   ` Marc Zyngier
2023-06-12 16:59   ` Catalin Marinas
2023-06-12 16:59     ` Catalin Marinas
2023-06-13  8:25   ` Shaoqin Huang
2023-06-13  8:25     ` Shaoqin Huang
2023-06-09 16:21 ` [PATCH v3 03/17] arm64: Turn kaslr_feature_override into a generic SW feature override Marc Zyngier
2023-06-09 16:21   ` Marc Zyngier
2023-06-12 17:16   ` Catalin Marinas
2023-06-12 17:16     ` Catalin Marinas
2023-06-14  7:26   ` Shaoqin Huang
2023-06-14  7:26     ` Shaoqin Huang
2023-06-09 16:21 ` [PATCH v3 04/17] arm64: Add KVM_HVHE capability and has_hvhe() predicate Marc Zyngier
2023-06-09 16:21   ` Marc Zyngier
2023-06-12 17:24   ` Catalin Marinas
2023-06-12 17:24     ` Catalin Marinas
2023-06-14  7:32   ` Shaoqin Huang
2023-06-14  7:35   ` Shaoqin Huang
2023-06-14  7:35     ` Shaoqin Huang
2023-06-14 16:06     ` Marc Zyngier
2023-06-14 16:06       ` Marc Zyngier
2023-06-09 16:21 ` [PATCH v3 05/17] arm64: Don't enable VHE for the kernel if OVERRIDE_HVHE is set Marc Zyngier
2023-06-09 16:21   ` Marc Zyngier
2023-06-12 19:12   ` Catalin Marinas
2023-06-12 19:12     ` Catalin Marinas
2023-06-12 19:20     ` Oliver Upton
2023-06-12 19:20       ` Oliver Upton
2023-06-09 16:21 ` [PATCH v3 06/17] arm64: Allow EL1 physical timer access when running VHE Marc Zyngier
2023-06-09 16:21   ` Marc Zyngier
2023-06-12 19:14   ` Catalin Marinas
2023-06-12 19:14     ` Catalin Marinas
2023-06-09 16:21 ` [PATCH v3 07/17] arm64: Use CPACR_EL1 format to set CPTR_EL2 when E2H is set Marc Zyngier
2023-06-09 16:21   ` Marc Zyngier
2023-06-12 19:15   ` Catalin Marinas
2023-06-12 19:15     ` Catalin Marinas
2023-06-09 16:21 ` [PATCH v3 08/17] KVM: arm64: Remove alternatives from sysreg accessors in VHE hypervisor context Marc Zyngier
2023-06-09 16:21   ` Marc Zyngier
2023-06-09 16:21 ` [PATCH v3 09/17] KVM: arm64: Key use of VHE instructions in nVHE code off ARM64_KVM_HVHE Marc Zyngier
2023-06-09 16:21   ` Marc Zyngier
2023-06-13  9:57   ` Shaoqin Huang
2023-06-13  9:57     ` Shaoqin Huang
2023-06-09 16:21 ` [PATCH v3 10/17] KVM: arm64: Force HCR_EL2.E2H when ARM64_KVM_HVHE is set Marc Zyngier
2023-06-09 16:21   ` Marc Zyngier
2023-06-09 16:21 ` [PATCH v3 11/17] KVM: arm64: Disable TTBR1_EL2 when using ARM64_KVM_HVHE Marc Zyngier
2023-06-09 16:21   ` Marc Zyngier
2023-06-09 16:21 ` [PATCH v3 12/17] KVM: arm64: Adjust EL2 stage-1 leaf AP bits when ARM64_KVM_HVHE is set Marc Zyngier
2023-06-09 16:21   ` Marc Zyngier
2023-06-09 16:21 ` [PATCH v3 13/17] KVM: arm64: Rework CPTR_EL2 programming for HVHE configuration Marc Zyngier
2023-06-09 16:21   ` Marc Zyngier
2023-06-09 16:21 ` [PATCH v3 14/17] KVM: arm64: Program the timer traps with VHE layout in hVHE mode Marc Zyngier
2023-06-09 16:21   ` Marc Zyngier
2023-06-09 16:21 ` [PATCH v3 15/17] KVM: arm64: Force HCR_E2H in guest context when ARM64_KVM_HVHE is set Marc Zyngier
2023-06-09 16:21   ` Marc Zyngier
2023-06-09 16:21 ` [PATCH v3 16/17] arm64: Allow arm64_sw.hvhe on command line Marc Zyngier
2023-06-09 16:21   ` Marc Zyngier
2023-06-12 19:16   ` Catalin Marinas
2023-06-12 19:16     ` Catalin Marinas
2023-06-09 16:22 ` [PATCH v3 17/17] KVM: arm64: Terrible timer hack for M1 with hVHE Marc Zyngier
2023-06-09 16:22   ` Marc Zyngier
2023-06-09 16:54 ` [PATCH v3 00/17] KVM: arm64: Allow using VHE in the nVHE hypervisor Marc Zyngier
2023-06-09 16:54   ` Marc Zyngier
2023-06-14 15:31 ` (subset) " Oliver Upton
2023-06-14 15:31   ` Oliver Upton
2023-06-14 16:16   ` Marc Zyngier
2023-06-14 16:16     ` Marc Zyngier
2024-07-10  6:45 ` Tangnianyao
2024-07-10  8:51   ` 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=86zfqp3a0j.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=guoyang2@huawei.com \
    --cc=james.morse@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=oliver.upton@linux.dev \
    --cc=qperret@google.com \
    --cc=suzuki.poulose@arm.com \
    --cc=tabba@google.com \
    --cc=tangnianyao@huawei.com \
    --cc=will@kernel.org \
    --cc=yuzenghui@huawei.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 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.