xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Juergen Gross <jgross@suse.com>, xen-devel@lists.xen.org
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
	George.Dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
	ian.jackson@eu.citrix.com, tim@xen.org, jbeulich@suse.com
Subject: Re: [PATCH v3 2/2] xen: add update indicator to vcpu_runstate_info
Date: Mon, 20 Jun 2016 18:36:24 +0100	[thread overview]
Message-ID: <57682998.4030104@arm.com> (raw)
In-Reply-To: <1466141184-28876-3-git-send-email-jgross@suse.com>

Hi Juergen,

On 17/06/16 06:26, Juergen Gross wrote:
> In order to support reading another vcpu's mapped vcpu_runstate_info
> an indicator for an occurring update of the runstate information is
> needed.
> Add the possibility to activate setting this indicator in the highest
> bit of state_entry_time via a vm_assist hypercall. When activated the
> update indicator will be set before the runstate information is
> modified in guest memory and it will be reset after modification is
> done. As state_entry_time is guaranteed to be different after each
> update the guest can detect any update (either in progress or while
> reading the runstate data) by comparing state_entry_time before and
> after reading runstate data: in case the values differ or the update
> indicator was set the data might be inconsistent and should be reread.
> Signed-off-by: Juergen Gross <jgross@suse.com>

For the ARM bits:

Acked-by: Julien Grall <julien.grall@arm.com>


Julien Grall

Xen-devel mailing list

      parent reply	other threads:[~2016-06-20 17:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-17  5:26 [PATCH v3 0/2] Support consistent reads of mapped vcpu_runstate_info Juergen Gross
2016-06-17  5:26 ` [PATCH v3 1/2] xen/arm: add support for vm_assist hypercall Juergen Gross
2016-06-17  5:26 ` [PATCH v3 2/2] xen: add update indicator to vcpu_runstate_info Juergen Gross
2016-06-17  8:03   ` Jan Beulich
2016-06-20 17:36   ` Julien Grall [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57682998.4030104@arm.com \
    --to=julien.grall@arm.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \


* 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).