From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Will Deacon <will@kernel.org>, linux-arm-kernel@lists.infradead.org
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Steven Price <steven.price@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Marc Zyngier <maz@kernel.org>,
linux-coco@lists.linux.dev
Subject: Re: [PATCH 0/6] Support for running as a pKVM protected guest
Date: Wed, 31 Jul 2024 14:55:13 +0100 [thread overview]
Message-ID: <7bbe63b9-339f-4a67-bde6-1a5f01da36a4@arm.com> (raw)
In-Reply-To: <20240730151113.1497-1-will@kernel.org>
Hi Will,
On 30/07/2024 16:11, Will Deacon wrote:
> Hi folks,
>
> Since the patches for running as a CCA guest were posted already at [1],
> I figured it was worth posting the equivalent pKVM changes needed to run
> as a protected guest under an Android host kernel. In particular, I've
> tried to structure the code so that the CCA patches can use the same
> hooks. I'd welcome feedback from the CCA developers (i.e. Steven and
> Suzuki) as to whether this is sufficient.
Thanks for the patches ! The hooks for set_memory_*crypted() and the
ioremap_prot() looks fitting for the CCA support. We will cherry pick
those and base our next version on it. On a side note, this doesn't
solve the "fixmap" for earlycon. Hopefully, we can push something
based on this in the coming weeks.
Kind regards
Suzuki
>
> There are also some pKVM-specific details which are worth discussion:
>
> * I've kept the code compatible with Android, so these patches allow
> an upstream kernel to run as a protected guest on a production
> (unlocked) Android device. This seemed like a good property for v1,
> but I'm happy to break compatibility if folks prefer a cleaner
> interface (e.g. using consecutive hypercall numbers).
>
> * I've included only the hypercalls that are necessary for a
> functioning guest. Android has some others, but I'd prefer to land
> the host support upstream before we expose optional interfaces as
> ABI.
>
> * For now, the stage-2 page size cannot be larger than the guest
> stage-1 page size otherwise the guest will fail to boot.
>
> * I don't forcefully configure SWIOTLB, as we rely on Restricted DMA
> pools (CONFIG_DMA_RESTRICTED_POOL) for devices that need it.
>
> I also pushed a branch at [2] based on -rc1.
>
> Cheers,
>
> Will
>
> [1] https://lore.kernel.org/r/20240701095505.165383-1-steven.price@arm.com
> [2] git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git kvm/protected-guest
>
> Cc: Sudeep Holla <sudeep.holla@arm.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>
> Cc: Suzuki Poulose <suzuki.poulose@arm.com>
> Cc: Steven Price <steven.price@arm.com>
> Cc: Oliver Upton <oliver.upton@linux.dev>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: linux-coco@lists.linux.dev
>
> --->8
>
> Marc Zyngier (1):
> firmware/smccc: Call arch-specific hook on discovering KVM services
>
> Will Deacon (5):
> drivers/virt: pkvm: Add initial support for running as a protected
> guest
> arm64: mm: Add top-level dispatcher for internal mem_encrypt API
> drivers/virt: pkvm: Hook up mem_encrypt API using pKVM hypercalls
> arm64: mm: Add confidential computing hook to ioremap_prot()
> drivers/virt: pkvm: Intercept ioremap using pKVM MMIO_GUARD hypercall
>
> Documentation/virt/kvm/arm/hypercalls.rst | 98 ++++++++++++++
> arch/arm/include/asm/hypervisor.h | 2 +
> arch/arm64/Kconfig | 1 +
> arch/arm64/include/asm/hypervisor.h | 11 ++
> arch/arm64/include/asm/io.h | 4 +
> arch/arm64/include/asm/mem_encrypt.h | 15 +++
> arch/arm64/include/asm/set_memory.h | 1 +
> arch/arm64/mm/Makefile | 2 +-
> arch/arm64/mm/ioremap.c | 23 +++-
> arch/arm64/mm/mem_encrypt.c | 50 +++++++
> drivers/firmware/smccc/kvm_guest.c | 2 +
> drivers/virt/coco/Kconfig | 2 +
> drivers/virt/coco/Makefile | 1 +
> drivers/virt/coco/pkvm-guest/Kconfig | 10 ++
> drivers/virt/coco/pkvm-guest/Makefile | 2 +
> drivers/virt/coco/pkvm-guest/arm-pkvm-guest.c | 127 ++++++++++++++++++
> include/linux/arm-smccc.h | 28 ++++
> 17 files changed, 377 insertions(+), 2 deletions(-)
> create mode 100644 arch/arm64/include/asm/mem_encrypt.h
> create mode 100644 arch/arm64/mm/mem_encrypt.c
> create mode 100644 drivers/virt/coco/pkvm-guest/Kconfig
> create mode 100644 drivers/virt/coco/pkvm-guest/Makefile
> create mode 100644 drivers/virt/coco/pkvm-guest/arm-pkvm-guest.c
>
next prev parent reply other threads:[~2024-07-31 13:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 15:11 [PATCH 0/6] Support for running as a pKVM protected guest Will Deacon
2024-07-30 15:11 ` [PATCH 1/6] firmware/smccc: Call arch-specific hook on discovering KVM services Will Deacon
2024-07-31 14:41 ` Aneesh Kumar K.V
2024-07-31 15:50 ` Will Deacon
2024-07-31 15:53 ` Aneesh Kumar K.V
2024-07-31 15:56 ` Aneesh Kumar K.V
2024-08-02 15:44 ` Catalin Marinas
2024-08-02 16:16 ` Aneesh Kumar K.V
2024-08-02 15:30 ` Suzuki K Poulose
2024-08-07 12:43 ` Suzuki K Poulose
2024-08-23 13:13 ` Will Deacon
2024-08-02 15:13 ` Catalin Marinas
2024-07-30 15:11 ` [PATCH 2/6] drivers/virt: pkvm: Add initial support for running as a protected guest Will Deacon
2024-07-30 15:11 ` [PATCH 3/6] arm64: mm: Add top-level dispatcher for internal mem_encrypt API Will Deacon
2024-07-30 15:11 ` [PATCH 4/6] drivers/virt: pkvm: Hook up mem_encrypt API using pKVM hypercalls Will Deacon
2024-08-21 16:49 ` Marc Zyngier
2024-08-23 15:41 ` Will Deacon
2024-08-23 16:53 ` Marc Zyngier
2024-07-30 15:11 ` [PATCH 5/6] arm64: mm: Add confidential computing hook to ioremap_prot() Will Deacon
2024-07-30 15:11 ` [PATCH 6/6] drivers/virt: pkvm: Intercept ioremap using pKVM MMIO_GUARD hypercall Will Deacon
2024-07-31 13:24 ` Aneesh Kumar K.V
2024-07-31 13:55 ` Suzuki K Poulose [this message]
2024-07-31 15:52 ` [PATCH 0/6] Support for running as a pKVM protected guest Will Deacon
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=7bbe63b9-339f-4a67-bde6-1a5f01da36a4@arm.com \
--to=suzuki.poulose@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-coco@lists.linux.dev \
--cc=lpieralisi@kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=steven.price@arm.com \
--cc=sudeep.holla@arm.com \
--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).