On 01/08/2012 04:52 PM, Alexander Graf wrote:
> On 08.01.2012, at 14:13, Avi Kivity wrote:
>
> > On 01/04/2012 03:10 AM, Alexander Graf wrote:
> >> From: Scott Wood <scottwood@xxxxxxxxxxxxx>
> >>
> >> This implements a shared-memory API for giving host userspace access to
> >> the guest's TLB.
> >>
> >>
> >> +4.59 KVM_DIRTY_TLB
> >> +
> >> +Capability: KVM_CAP_SW_TLB
> >> +Architectures: ppc
> >> +Type: vcpu ioctl
> >> +Parameters: struct kvm_dirty_tlb (in)
> >> +Returns: 0 on success, -1 on error
> >> +
> >> +struct kvm_dirty_tlb {
> >> + __u64 bitmap;
> >> + __u32 num_dirty;
> >> +};
> >
> > Changes size with 32/64 bit userspace - is this an issue on this subarch?
>
> #include <stdio.h>
>
> int main(int argc, char **argv)
> {
> struct x {
> long long a;
> int b;
> } x;
>
> printf("%d\n", sizeof(x));
>
> return 0;
> }
>
> ---
>
> agraf@lychee:/dev/shm> gcc align.c -o align -m64
> agraf@lychee:/dev/shm> ./align
> 16
> agraf@lychee:/dev/shm> gcc align.c -o align -m32
> agraf@lychee:/dev/shm> ./align
> 16
Okay - I guess it's different to x86. And I think we had this
conversation before...
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
