[lkml]   [2002]   [Oct]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] linux-2.5.43_vsyscall_A0

    > > > Since no one really brought up any issues with the code itself
    > > > (correct me if I'm wrong), here is the i386 vsyscall gettimeofday port
    > > > I sent last night, synced up and ready for integration.
    > >
    > > This vsyscall implementation breaks UML. Any app that's run inside UML
    > > that uses vsyscalls will get the host's vsyscalls rather than the UML
    > > vsyscalls.
    > Ugh.
    > Guess you'll have some problems then with UML on x86-64, which always uses
    > vgettimeofday. But it's only used for gettimeofday() currently, perhaps it's
    > not that bad when the UML child runs with the host's time.

    Well, if you want to use UML for time shifting (pretty common use,

    > I guess it would be possible to add some support for UML
    > to map own code over the vsyscall reserved locations. UML would need
    > to use the syscalls then. But it'll be likely ugly.

    I guess this is the right solution. [Or UML could simply unmap that
    area and handle the faults...].
    Worst form of spam? Adding advertisment signatures ala
    What goes next? Inserting advertisment *into* email?
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

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