[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6581a6e8-45c9-a80c-d2a4-33466f5712fd@arm.com>
Date: Fri, 18 Oct 2019 09:32:09 +0100
From: Vincenzo Frascino <vincenzo.frascino@....com>
To: Andy Lutomirski <luto@...nel.org>, Huacai Chen <chenhc@...ote.com>,
Maxime Bizon <mbizon@...ebox.fr>
Cc: Thomas Gleixner <tglx@...utronix.de>, chenhuacai@...il.com,
LKML <linux-kernel@...r.kernel.org>,
stable <stable@...r.kernel.org>, Arnd Bergmann <arnd@...db.de>,
Paul Burton <paul.burton@...s.com>, linux-mips@...r.kernel.org,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] lib/vdso: Use __arch_use_vsyscall() to indicate fallback
Hi Andy and Hucan,
On 10/18/19 4:15 AM, Andy Lutomirski wrote:
> On Thu, Oct 17, 2019 at 7:57 PM Huacai Chen <chenhc@...ote.com> wrote:
>>
>> In do_hres(), we currently use whether the return value of __arch_get_
>> hw_counter() is negtive to indicate fallback, but this is not a good
>> idea. Because:
>>
>> 1, ARM64 returns ULL_MAX but MIPS returns 0 when clock_mode is invalid;
>> 2, For a 64bit counter, a "negtive" value of counter is actually valid.
>
> s/negtive/negative
>
> What's the actual bug? Is it that MIPS is returning 0 but the check
> is < 0? Sounds like MIPS should get fixed.
>
I submitted a patch for this yesterday to the MIPS maintainers [1]. The MIPS32
r1 implementation had a bug when VDSO_CLOCK_NONE was set.
The issue has been reported by Maxime Bizon who tested the fix as well.
[1] https://patchwork.kernel.org/patch/11193391/
--
Regards,
Vincenzo
Powered by blists - more mailing lists