kvmarm.lists.cs.columbia.edu archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Steven Price <steven.price@arm.com>
Cc: kvm@vger.kernel.org, Marc Zyngier <maz@kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Russell King <linux@armlinux.org.uk>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Will Deacon <will@kernel.org>,
	kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 10/10] arm64: Retrieve stolen time as paravirtualized guest
Date: Fri, 25 Oct 2019 16:57:08 +0100	[thread overview]
Message-ID: <20191025155708.GB999@C02TF0J2HF1T.local> (raw)
In-Reply-To: <20191021152823.14882-11-steven.price@arm.com>

On Mon, Oct 21, 2019 at 04:28:23PM +0100, Steven Price wrote:
> Enable paravirtualization features when running under a hypervisor
> supporting the PV_TIME_ST hypercall.
> 
> For each (v)CPU, we ask the hypervisor for the location of a shared
> page which the hypervisor will use to report stolen time to us. We set
> pv_time_ops to the stolen time function which simply reads the stolen
> value from the shared page for a VCPU. We guarantee single-copy
> atomicity using READ_ONCE which means we can also read the stolen
> time for another VCPU than the currently running one while it is
> potentially being updated by the hypervisor.
> 
> Signed-off-by: Steven Price <steven.price@arm.com>

Acked-by: Catalin Marinas <catalin.marinas@arm.com>
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

  reply	other threads:[~2019-10-25 15:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 15:28 [PATCH v7 00/10] arm64: Stolen time support Steven Price
2019-10-21 15:28 ` [PATCH v7 01/10] KVM: arm64: Document PV-time interface Steven Price
2019-10-21 15:28 ` [PATCH v7 02/10] KVM: arm/arm64: Factor out hypercall handling from PSCI code Steven Price
2019-10-21 15:28 ` [PATCH v7 03/10] KVM: arm64: Implement PV_TIME_FEATURES call Steven Price
2019-10-21 15:28 ` [PATCH v7 04/10] KVM: Implement kvm_put_guest() Steven Price
2019-10-21 15:28 ` [PATCH v7 05/10] KVM: arm64: Support stolen time reporting via shared structure Steven Price
2019-10-21 15:28 ` [PATCH v7 06/10] KVM: Allow kvm_device_ops to be const Steven Price
2019-10-21 15:28 ` [PATCH v7 07/10] KVM: arm64: Provide VCPU attributes for stolen time Steven Price
2019-10-21 15:28 ` [PATCH v7 08/10] arm/arm64: Provide a wrapper for SMCCC 1.1 calls Steven Price
2019-10-21 15:28 ` [PATCH v7 09/10] arm/arm64: Make use of the SMCCC 1.1 wrapper Steven Price
2019-10-25 15:50   ` Catalin Marinas
2019-10-21 15:28 ` [PATCH v7 10/10] arm64: Retrieve stolen time as paravirtualized guest Steven Price
2019-10-25 15:57   ` Catalin Marinas [this message]
2019-10-21 18:37 ` [PATCH v7 00/10] arm64: Stolen time support Marc Zyngier
2019-10-23 12:39 ` Marc Zyngier
2019-10-23 13:50   ` Steven Price

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=20191025155708.GB999@C02TF0J2HF1T.local \
    --to=catalin.marinas@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=maz@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=steven.price@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).