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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- From: Zoltan Menyhart <[email protected]>
- Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- References:
- FOR REVIEW: New x86-64 vsyscall vgetcpu()
- From: Andi Kleen <[email protected]>
- Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- From: Andi Kleen <[email protected]>
- Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- From: Jes Sorensen <[email protected]>
- Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- From: Andi Kleen <[email protected]>
- Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- From: Jes Sorensen <[email protected]>
- Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- From: Zoltan Menyhart <[email protected]>
- FOR REVIEW: New x86-64 vsyscall vgetcpu()
- Prev by Date: [RESEND][PATCH] Let even non-dumpable tasks access /proc/self/fd
- Next by Date: Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- Previous by thread: Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- Next by thread: Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- Index(es):
 |