Re: [XenPPC] Re: libvirt status of bugt racking regarding bad paddr (patch)

2007-07-02 Thread Christian Ehrhardt
The change that brought the 64bit padded structures was this one: changeset: 13594:30af6cfdb05c user:[EMAIL PROTECTED] date:Wed Jan 24 16:33:19 2007 + summary: Make domctl/sysctl interfaces 32-/64-bit invariant. It lifted the interface version to 5 which fits to the

Re: [XenPPC] Re: libvirt status of bugt racking regarding bad paddr (verification + question)

2007-06-29 Thread Christian Ehrhardt
I verified my endian/32/64bit based assumption. Time runs short today - in order that no one overlooks the questions I hope to read some comments on monday I put them here to the head ;) - Do we need a compat wrapper for the syscall here? Or do we have one already, but it is not used? - Should

Re: [XenPPC] Re: libvirt status of bugt racking regarding bad paddr (ugly fix attached)

2007-06-28 Thread Christian Ehrhardt
Anyone not interested in how I came to the fix might want to read just the last few paragraphs of this response. First of all dominfos is a output structure so it is ok if it is zeroed, but all the pointers/structures need to be valid. It is also a union so the effect of having the same adresses

[XenPPC] Re: libvirt status of bugt racking regarding bad paddr

2007-06-27 Thread Christian Ehrhardt
This is how the adresses are passed through the stack: (read this monospaced) userspace-libvirt linux-kernel Xen alloc/ioctl -incoming - xencomm_map- incoming - xencomm_inline_to_guest 0xffba2eb0 -