From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: arch_set_info_guest() producing inconsistent state on x86? Date: Tue, 29 Mar 2011 10:59:14 +0100 Message-ID: References: <4D91AE140200007800038CF7@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4D91AE140200007800038CF7@vpn.id2.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 29/03/2011 09:01, "Jan Beulich" 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