[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] arch_set_info_guest() producing inconsistent state on x86?

  • To: Jan Beulich <JBeulich@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.xen@xxxxxxxxx>
  • Date: Tue, 29 Mar 2011 10:59:14 +0100
  • Cc:
  • Delivery-date: Tue, 29 Mar 2011 03:00:47 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=rP1DqBppdM+WPRF0m2h/WCOIq9IpCz8sKmE1rwXzrtSPjbKXn3VBW8g11BX1AWaeYT fVv6LOx2XfA4KcSg5LUPOS2B/uyqQL1lofZMd3EmiYSib7ioAUljyGUWYfYyFN9DdJMe CSIYY6kV0/HgKmNEN6ypeLyhvYosVDGTze4Z0=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acvt9/VmuSHnX/nXrk249HOg9RwL+A==
  • Thread-topic: [Xen-devel] arch_set_info_guest() producing inconsistent state on x86?
On 29/03/2011 09:01, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:

> The question is whether it must be considered legal to issue
> XEN_DOMCTL_setvcpucontext on an already initialized vCPU
> in the first place.

It's probably used by debuggers running in dom0? Also see
modify_returncode() in libxc/xc_resume.c -- so it's used on suspend resume
in the failure case.

I doubt anything other than GPRs are ever modified after first
initialisation.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.