> > > 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,
AFAICS)...
> 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...].
Pavel
-- Worst form of spam? Adding advertisment signatures ala sourceforge.net. 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 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/