Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: suzuki.poulose@arm.com, james.morse@arm.com,
	catalin.marinas@arm.com, will@kernel.org,
	Quentin Perret <qperret@google.com>,
	alexandru.elisei@arm.com
Cc: kernel-team@android.com, kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/7] KVM: arm64: Reduce hyp_vmemmap overhead
Date: Fri, 11 Jun 2021 13:27:57 +0100	[thread overview]
Message-ID: <162341446985.1357134.6545944671032237373.b4-ty@kernel.org> (raw)
In-Reply-To: <20210608114518.748712-1-qperret@google.com>

On Tue, 8 Jun 2021 11:45:11 +0000, Quentin Perret wrote:
> This is a v3 of the patch series previously posted here:
> 
>   https://lore.kernel.org/r/20210602094347.3730846-1-qperret@google.com
> 
> Please refer to the cover letter of v1 for the context and motivation
> behind the series.
> 
> [...]

Applied to next, thanks!

[1/7] KVM: arm64: Move hyp_pool locking out of refcount helpers
      commit: 6cbf874e51b68e5b2eb0cc50be3676f5d5601dab
[2/7] KVM: arm64: Use refcount at hyp to check page availability
      commit: 581982decc635c93934aaeb88d62c21238c63f11
[3/7] KVM: arm64: Remove list_head from hyp_page
      commit: 914cde58a03cc5eef858db34687433e17d0e44be
[4/7] KVM: arm64: Unify MMIO and mem host stage-2 pools
      commit: 7c350ea39e53ade33ca7be00b0947f2b9f53dda0
[5/7] KVM: arm64: Remove hyp_pool pointer from struct hyp_page
      commit: d978b9cfe6fe8008467f8c5d51677f52e7815b39
[6/7] KVM: arm64: Use less bits for hyp_page order
      commit: 87ec0606733e1aa9568f54ddb41f03aa6b5687f2
[7/7] KVM: arm64: Use less bits for hyp_page refcount
      commit: 6929586d8eddad184f43526efe7bf0a8be4f18b2

Cheers,

	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

      parent reply	other threads:[~2021-06-11 12:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 11:45 [PATCH v3 0/7] KVM: arm64: Reduce hyp_vmemmap overhead Quentin Perret
2021-06-08 11:45 ` [PATCH v3 1/7] KVM: arm64: Move hyp_pool locking out of refcount helpers Quentin Perret
2021-06-08 11:45 ` [PATCH v3 2/7] KVM: arm64: Use refcount at hyp to check page availability Quentin Perret
2021-06-08 11:45 ` [PATCH v3 3/7] KVM: arm64: Remove list_head from hyp_page Quentin Perret
2021-06-08 11:45 ` [PATCH v3 4/7] KVM: arm64: Unify MMIO and mem host stage-2 pools Quentin Perret
2021-06-08 11:45 ` [PATCH v3 5/7] KVM: arm64: Remove hyp_pool pointer from struct hyp_page Quentin Perret
2021-06-08 11:45 ` [PATCH v3 6/7] KVM: arm64: Use less bits for hyp_page order Quentin Perret
2021-06-08 11:45 ` [PATCH v3 7/7] KVM: arm64: Use less bits for hyp_page refcount Quentin Perret
2021-06-11 12:27 ` 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=162341446985.1357134.6545944671032237373.b4-ty@kernel.org \
    --to=maz@kernel.org \
    --cc=alexandru.elisei@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=kernel-team@android.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qperret@google.com \
    --cc=suzuki.poulose@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