From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: kernel-team@android.com, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/6] KVM/arm64: Minor/trivial fixes from pKVM mega-patch
Date: Thu, 09 Jun 2022 13:19:47 +0100 [thread overview]
Message-ID: <878rq63u70.wl-maz@kernel.org> (raw)
In-Reply-To: <20220609121223.2551-1-will@kernel.org>
On Thu, 09 Jun 2022 13:12:17 +0100,
Will Deacon <will@kernel.org> wrote:
>
> Hi folks,
>
> These six KVM/arm64 patches are very minor fixes (including "fixes" to
> comments) which were previously posted as part of the pKVM mega-patch
> but which can be merged independently of the rest of that. Marc -- I'm
> not sure whether it's even worth taking these for 5.19, but here they
> are so you can have a look and decide yourself.
They are all tragically simple, and patch 2 actually qualifies as a
fix (a legitimate guest would fail to run correctly).
Also, the pKVM series could do with a bit of diet, so I'm inclined to
take these in right now.
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: kvmarm@lists.cs.columbia.edu,
Alexandru Elisei <alexandru.elisei@arm.com>,
kernel-team@android.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/6] KVM/arm64: Minor/trivial fixes from pKVM mega-patch
Date: Thu, 09 Jun 2022 13:19:47 +0100 [thread overview]
Message-ID: <878rq63u70.wl-maz@kernel.org> (raw)
In-Reply-To: <20220609121223.2551-1-will@kernel.org>
On Thu, 09 Jun 2022 13:12:17 +0100,
Will Deacon <will@kernel.org> wrote:
>
> Hi folks,
>
> These six KVM/arm64 patches are very minor fixes (including "fixes" to
> comments) which were previously posted as part of the pKVM mega-patch
> but which can be merged independently of the rest of that. Marc -- I'm
> not sure whether it's even worth taking these for 5.19, but here they
> are so you can have a look and decide yourself.
They are all tragically simple, and patch 2 actually qualifies as a
fix (a legitimate guest would fail to run correctly).
Also, the pKVM series could do with a bit of diet, so I'm inclined to
take these in right now.
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-09 12:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 12:12 [PATCH 0/6] KVM/arm64: Minor/trivial fixes from pKVM mega-patch Will Deacon
2022-06-09 12:12 ` Will Deacon
2022-06-09 12:12 ` [PATCH 1/6] KVM: arm64: Return error from kvm_arch_init_vm() on allocation failure Will Deacon
2022-06-09 12:12 ` Will Deacon
2022-06-09 12:12 ` [PATCH 2/6] KVM: arm64: Handle all ID registers trapped for a protected VM Will Deacon
2022-06-09 12:12 ` Will Deacon
2022-06-14 5:57 ` Reiji Watanabe
2022-06-14 5:57 ` Reiji Watanabe
2022-06-09 12:12 ` [PATCH 3/6] KVM: arm64: Ignore 'kvm-arm.mode=protected' when using VHE Will Deacon
2022-06-09 12:12 ` Will Deacon
2022-06-09 12:12 ` [PATCH 4/6] KVM: arm64: Extend comment in has_vhe() Will Deacon
2022-06-09 12:12 ` Will Deacon
2022-06-09 12:12 ` [PATCH 5/6] KVM: arm64: Remove redundant hyp_assert_lock_held() assertions Will Deacon
2022-06-09 12:12 ` Will Deacon
2022-06-09 12:12 ` [PATCH 6/6] KVM: arm64: Drop stale comment Will Deacon
2022-06-09 12:12 ` Will Deacon
2022-06-09 12:19 ` Marc Zyngier [this message]
2022-06-09 12:19 ` [PATCH 0/6] KVM/arm64: Minor/trivial fixes from pKVM mega-patch Marc Zyngier
2022-06-09 12:26 ` Marc Zyngier
2022-06-09 12:26 ` Marc Zyngier
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=878rq63u70.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.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 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.