lkml.org 
[lkml]   [2006]   [Jun]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: FOR REVIEW: New x86-64 vsyscall vgetcpu()
    On Fri, 16 Jun 2006, Zoltan Menyhart wrote:

    > 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.

    I think it's probably best to leave most of the stuff in task_struct
    private (ie, mapped in kernel only).

    > Thanks,
    >
    > Zoltan

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

    \
     
     \ /
      Last update: 2006-06-16 23:07    [W:0.023 / U:64.004 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site