All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Upton <oliver.upton@linux.dev>
To: Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
	Alexandru Elisei <alexandru.elisei@arm.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.linux.dev,
	Will Deacon <will@kernel.org>,
	kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] KVM: arm64: pKVM memory transitions cleanup
Date: Fri, 28 Oct 2022 08:34:46 +0000	[thread overview]
Message-ID: <20221028083448.1998389-1-oliver.upton@linux.dev> (raw)

In order to help resolve my own bikeshedding on the outstanding pKVM
patches [1], small deck of patches to polish up the existing memory
transitions. Mainly:

 - Rejig the layout of pkvm_mem_transition
 - Stop using out pointers to get at the 'completer' addr
 - Use better-fitting terminology (source/target) to describe the
   addresses involved in a memory transition

Applies to 6.1-rc2. Politely compile tested, and that's just about it.

Oliver Upton (2):
  KVM: arm64: Clean out the odd handling of completer_addr
  KVM: arm64: Redefine pKVM memory transitions in terms of source/target

 arch/arm64/kvm/hyp/nvhe/mem_protect.c | 124 +++++++++++---------------
 1 file changed, 52 insertions(+), 72 deletions(-)


base-commit: 247f34f7b80357943234f93f247a1ae6b6c3a740
-- 
2.38.1.273.g43a17bfeac-goog

_______________________________________________
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: Oliver Upton <oliver.upton@linux.dev>
To: Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
	Alexandru Elisei <alexandru.elisei@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
	Quentin Perret <qperret@google.com>,
	kvmarm@lists.linux.dev, Will Deacon <will@kernel.org>,
	Fuad Tabba <tabba@google.com>,
	Vincent Donnefort <vdonnefort@google.com>,
	Oliver Upton <oliver.upton@linux.dev>
Subject: [PATCH 0/2] KVM: arm64: pKVM memory transitions cleanup
Date: Fri, 28 Oct 2022 08:34:46 +0000	[thread overview]
Message-ID: <20221028083448.1998389-1-oliver.upton@linux.dev> (raw)
Message-ID: <20221028083446.y5StoZSnUpbTAH1SEfUduz4HaWclSY3EQmY-WFaRNkA@z> (raw)

In order to help resolve my own bikeshedding on the outstanding pKVM
patches [1], small deck of patches to polish up the existing memory
transitions. Mainly:

 - Rejig the layout of pkvm_mem_transition
 - Stop using out pointers to get at the 'completer' addr
 - Use better-fitting terminology (source/target) to describe the
   addresses involved in a memory transition

Applies to 6.1-rc2. Politely compile tested, and that's just about it.

Oliver Upton (2):
  KVM: arm64: Clean out the odd handling of completer_addr
  KVM: arm64: Redefine pKVM memory transitions in terms of source/target

 arch/arm64/kvm/hyp/nvhe/mem_protect.c | 124 +++++++++++---------------
 1 file changed, 52 insertions(+), 72 deletions(-)


base-commit: 247f34f7b80357943234f93f247a1ae6b6c3a740
-- 
2.38.1.273.g43a17bfeac-goog


WARNING: multiple messages have this Message-ID (diff)
From: Oliver Upton <oliver.upton@linux.dev>
To: Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
	Alexandru Elisei <alexandru.elisei@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
	Quentin Perret <qperret@google.com>,
	kvmarm@lists.linux.dev, Will Deacon <will@kernel.org>,
	Fuad Tabba <tabba@google.com>,
	Vincent Donnefort <vdonnefort@google.com>,
	Oliver Upton <oliver.upton@linux.dev>
Subject: [PATCH 0/2] KVM: arm64: pKVM memory transitions cleanup
Date: Fri, 28 Oct 2022 08:34:46 +0000	[thread overview]
Message-ID: <20221028083448.1998389-1-oliver.upton@linux.dev> (raw)

In order to help resolve my own bikeshedding on the outstanding pKVM
patches [1], small deck of patches to polish up the existing memory
transitions. Mainly:

 - Rejig the layout of pkvm_mem_transition
 - Stop using out pointers to get at the 'completer' addr
 - Use better-fitting terminology (source/target) to describe the
   addresses involved in a memory transition

Applies to 6.1-rc2. Politely compile tested, and that's just about it.

Oliver Upton (2):
  KVM: arm64: Clean out the odd handling of completer_addr
  KVM: arm64: Redefine pKVM memory transitions in terms of source/target

 arch/arm64/kvm/hyp/nvhe/mem_protect.c | 124 +++++++++++---------------
 1 file changed, 52 insertions(+), 72 deletions(-)


base-commit: 247f34f7b80357943234f93f247a1ae6b6c3a740
-- 
2.38.1.273.g43a17bfeac-goog


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2022-10-28  8:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28  8:34 Oliver Upton [this message]
2022-10-28  8:34 ` [PATCH 0/2] KVM: arm64: pKVM memory transitions cleanup Oliver Upton
2022-10-28  8:34 ` Oliver Upton
2022-10-28  8:34 ` [PATCH 1/2] KVM: arm64: Clean out the odd handling of completer_addr Oliver Upton
2022-10-28  8:34   ` Oliver Upton
2022-10-28  8:34   ` Oliver Upton
2022-11-10 10:42   ` Will Deacon
2022-11-10 10:42     ` Will Deacon
2022-11-10 10:42     ` Will Deacon
2022-10-28  8:34 ` [PATCH 2/2] KVM: arm64: Redefine pKVM memory transitions in terms of source/target Oliver Upton
2022-10-28  8:34   ` Oliver Upton
2022-10-28  8:34   ` Oliver Upton
2022-10-28  9:57   ` Quentin Perret
2022-10-28  9:57     ` Quentin Perret
2022-10-28  9:57     ` Quentin Perret
2022-10-28 10:23     ` Oliver Upton
2022-10-28 10:23       ` Oliver Upton
2022-10-28 10:23       ` Oliver Upton
2022-11-10 10:46       ` Will Deacon
2022-11-10 10:46         ` Will Deacon
2022-11-10 10:46         ` 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=20221028083448.1998389-1-oliver.upton@linux.dev \
    --to=oliver.upton@linux.dev \
    --cc=alexandru.elisei@arm.com \
    --cc=james.morse@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maz@kernel.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.