[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABeXuvqvyeXYZMj05bfeKOgBK5i3mK6imsD2iNFfKES1kTjUng@mail.gmail.com>
Date: Wed, 8 Nov 2017 12:14:12 -0800
From: Deepa Dinamani <deepa.kernel@...il.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Greentime Hu <green.hu@...il.com>,
Greentime <greentime@...estech.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-arch <linux-arch@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Jason Cooper <jason@...edaemon.net>,
Marc Zyngier <marc.zyngier@....com>,
Rob Herring <robh+dt@...nel.org>,
Networking <netdev@...r.kernel.org>,
Vincent Chen <vincentc@...estech.com>,
Palmer Dabbelt <palmer@...belt.com>
Subject: Re: [PATCH 16/31] nds32: VDSO support
> Do applications call into the vdso directly and expect to get a timespec
> out? If they always go through the C library as an intermediate, then
> the glibc clock_gettime() could do the conversion.
It is recommended that applications do not call vdso symbols directly.
According to manpage:
"If you're trying to call the vDSO in your own application rather than
using the C library, you're most likely doing it wrong."
-Deepa
Powered by blists - more mailing lists