From: Juergen Gross <jgross@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
Jan Beulich <JBeulich@suse.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
"George.Dunlap@eu.citrix.com" <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Supporting consistency of vcpu_runstate_info across cpus
Date: Thu, 19 May 2016 16:11:18 +0200 [thread overview]
Message-ID: <573DC986.1050804@suse.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1605191147580.2914@sstabellini-ThinkPad-X260>
On 19/05/16 12:48, Stefano Stabellini wrote:
> On Thu, 19 May 2016, Jan Beulich wrote:
>>>>> On 19.05.16 at 12:40, <sstabellini@kernel.org> wrote:
>>> On Thu, 19 May 2016, Juergen Gross wrote:
>>>>> Alternatively, the easiest way will probably be to add a new VMASSIST,
>>>>> which allows the guest to opt into the new behaviour.
>>>>
>>>> Aah, nice. Yes, this seems to be a sensible option.
>>>
>>> If you are referring to VM_ASSIST, it is only available on x86. I
>>> suggest we use a feature flag instead.
>>
>> A feature flag can only be checked by the guest, not set. How
>> about enabling VMASSIST for ARM?
>
> Sure
Stefano, if you want I can do this when adding the VMASSIST option.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-19 14:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 7:53 Supporting consistency of vcpu_runstate_info across cpus Juergen Gross
2016-05-19 8:09 ` Andrew Cooper
2016-05-19 8:49 ` Juergen Gross
2016-05-19 10:21 ` Dario Faggioli
2016-05-19 13:57 ` Roger Pau Monne
2016-05-19 10:40 ` Stefano Stabellini
2016-05-19 10:45 ` Jan Beulich
2016-05-19 10:48 ` Stefano Stabellini
2016-05-19 14:11 ` Juergen Gross [this message]
2016-05-19 16:54 ` Stefano Stabellini
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=573DC986.1050804@suse.com \
--to=jgross@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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.