Hi Paul,
On 25/06/2019 18:11, Paul Burton wrote:
> Hi Vincenzo,
>
> On Tue, Jun 25, 2019 at 12:16:55AM +0100, Vincenzo Frascino wrote:
>> In the end I concluded that all the errors seen here depend on the fact that
>> I
>> tested my vdso implementation on MIPS32el only (as stated in the cover
>
Hi Vincenzo,
On Tue, Jun 25, 2019 at 12:16:55AM +0100, Vincenzo Frascino wrote:
> In the end I concluded that all the errors seen here depend on the fact that I
> tested my vdso implementation on MIPS32el only (as stated in the cover letter)
> and that when I tried to compile a 32BIT binary on a 6
Hi Paul,
thank you for your review.
On 6/24/19 7:41 PM, Paul Burton wrote:
> Hello,
>
> On Mon, Jun 24, 2019 at 02:34:24AM +0200, Thomas Gleixner wrote:
>> I did not merge the ARM and MIPS parts as they lack any form of
>> acknowlegment from their maintainers. Please talk to those folks. If they
Hello,
On Mon, Jun 24, 2019 at 02:34:24AM +0200, Thomas Gleixner wrote:
> I did not merge the ARM and MIPS parts as they lack any form of
> acknowlegment from their maintainers. Please talk to those folks. If they
> ack/review the changes then I can pick them up and they go into 5.3 or they
> have
On 24/06/2019 15:49, Catalin Marinas wrote:
> On Mon, Jun 24, 2019 at 03:23:46PM +0100, Russell King wrote:
>> On Mon, Jun 24, 2019 at 04:18:28PM +0200, Thomas Gleixner wrote:
>>> Vincenzo,
>>>
>>> On Mon, 24 Jun 2019, Thomas Gleixner wrote:
>>>
I did not merge the ARM and MIPS parts as they l
On Mon, Jun 24, 2019 at 03:23:46PM +0100, Russell King wrote:
> On Mon, Jun 24, 2019 at 04:18:28PM +0200, Thomas Gleixner wrote:
> > Vincenzo,
> >
> > On Mon, 24 Jun 2019, Thomas Gleixner wrote:
> >
> > > I did not merge the ARM and MIPS parts as they lack any form of
> > > acknowlegment from the
On Mon, Jun 24, 2019 at 04:18:28PM +0200, Thomas Gleixner wrote:
> Vincenzo,
>
> On Mon, 24 Jun 2019, Thomas Gleixner wrote:
>
> > I did not merge the ARM and MIPS parts as they lack any form of
> > acknowlegment from their maintainers. Please talk to those folks. If they
> > ack/review the chang
Vincenzo,
On Mon, 24 Jun 2019, Thomas Gleixner wrote:
> I did not merge the ARM and MIPS parts as they lack any form of
> acknowlegment from their maintainers. Please talk to those folks. If they
> ack/review the changes then I can pick them up and they go into 5.3 or they
> have to go in a later
Hi Thomas,
On 24/06/2019 01:34, Thomas Gleixner wrote:
> Vincenzo,
>
> On Fri, 21 Jun 2019, Vincenzo Frascino wrote:
>> vDSO (virtual dynamic shared object) is a mechanism that the Linux
>> kernel provides as an alternative to system calls to reduce where
>> possible the costs in terms of cycles.
On Fri, 21 Jun 2019 10:52:27 +0100
Vincenzo Frascino wrote:
Hi,
> vDSO (virtual dynamic shared object) is a mechanism that the Linux
> kernel provides as an alternative to system calls to reduce where
> possible the costs in terms of cycles.
[ ... ]
Some numbers for the ARM(32) part:
I booted
On Sun, 23 Jun 2019, Andy Lutomirski wrote:
> On Sun, Jun 23, 2019 at 5:34 PM Thomas Gleixner wrote:
> > +GENERIC VDSO LIBRARY:
> > +M: Andy Lutomirksy
>
> Lutomirski, perhaps?
Ooops. Where did I copy that from?
> Although I do appreciate the opportunity to say "not me!" :)
You just gave
Vincenzo,
On Fri, 21 Jun 2019, Vincenzo Frascino wrote:
> vDSO (virtual dynamic shared object) is a mechanism that the Linux
> kernel provides as an alternative to system calls to reduce where
> possible the costs in terms of cycles.
> This is possible because certain syscalls like gettimeofday()
On Sun, Jun 23, 2019 at 5:34 PM Thomas Gleixner wrote:
> +GENERIC VDSO LIBRARY:
> +M: Andy Lutomirksy
Lutomirski, perhaps? Although I do appreciate the opportunity to say
"not me!" :)
vDSO (virtual dynamic shared object) is a mechanism that the Linux
kernel provides as an alternative to system calls to reduce where
possible the costs in terms of cycles.
This is possible because certain syscalls like gettimeofday() do
not write any data and return one or more values that are stor
14 matches
Mail list logo
