[lkml]   [2000]   [Mar]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [patch] vsyscall feature
    Andrea Arcangeli wrote:
    > So the data information won't be at a known location and even if userspace
    > disasseble the vsyscalls to find where the information is placed to read
    > it without passing thorugh the vsyscall table, userspace still will read
    > what we want to show (in your example you can show the cpuid that you
    > prefer).

    Good point. You can bet that some partial machine code evaluator would
    like to disassemble the vsyscall code and duplicate the equivalent in
    JIT generated code at some point, interleaved with caller optimisations...

    -- Jamie

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:56    [W:0.019 / U:3.988 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site