Re: [Xen-devel] [PATCH v8 4/6] arm/vm_event: get/set registers

[Julien Grall <julien.grall@xxxxxxx>]

On 06/07/16 08:43, Jan Beulich wrote:
> > > > On 05.07.16 at 20:37, <tamas.lengyel@xxxxxxxxxxxx> wrote:
> > +struct vm_event_regs_arm64 {
> > +    uint64_t x0;
> > +    uint64_t x1;
> > +    uint64_t x2;
> > +    uint64_t x3;
> > +    uint64_t x4;
> > +    uint64_t x5;
> > +    uint64_t x6;
> > +    uint64_t x7;
> > +    uint64_t x8;
> > +    uint64_t x9;
> > +    uint64_t x10;
> > +    uint64_t x11;
> > +    uint64_t x12;
> > +    uint64_t x13;
> > +    uint64_t x14;
> > +    uint64_t x15;
> > +    uint64_t x16;
> > +    uint64_t x17;
> > +    uint64_t x18;
> > +    uint64_t x19;
> > +    uint64_t x20;
> > +    uint64_t x21;
> > +    uint64_t x22;
> > +    uint64_t x23;
> > +    uint64_t x24;
> > +    uint64_t x25;
> > +    uint64_t x26;
> > +    uint64_t x27;
> > +    uint64_t x28;
> > +    uint64_t x29;
> > +    uint64_t x30;
> > +    uint64_t pc;
> > +};
> Isn't the stack pointer a fully separate register in aarch64?
It is. Actually, there are 2 stack pointers (one for the kernel, the 
other for userspace. See sp_el0 and sp_el1.
Regards,

--
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel