Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()

[Zoltan Menyhart]

Jes Sorensen wrote:
> Zoltan Menyhart wrote:
>
> > Just to make sure I understand it correctly...
> > Assuming I have allocated per CPU data (numa control, etc.) pointed at by:
>
>
> I think you misunderstood - vgetcpu is for userland usage, not within
> the kernel.
>
> Cheers,
> Jes
I did understand it as a user land stuff.
This is why I want to map the current task structure into the user space.
In user code, we could see the actual value of the "current->thread_info.cpu".
My "#define current ((struct task_struct *) 0x...)" is not the same as
the kernel's one.

Thanks,

Zoltan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/