WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: Xen/ia64 presentation


On 28 Apr 2005, at 09:32, Keir Fraser wrote:

struct xen_state: (now xen_regs) state which xen C/asm code could alter
struct vcpu_state: (now exec_domain) all virtual CPU state
struct arch_vcpu_state

("vcpu_regs" might not be good, since we could need to save other
context like software-controlled TLBs, and so "xen_state" would match
"vcpu_state".)

How about:

xen_regs/execution_context_t --> user_cpureg_state
  (registers visible from user space)

full_execution_context_t --> guest_vcpu_state
  (entire guest execution state; includes a user_cpureg_state)

The former isn't user_vcpureg_state because it contains registers visible from user space. Those are the same in number and format regardless of whether you are running natively on a real CPU or on a Xen-based virtual CPU.

 -- Keir


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