From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Maarten ter Huurne <maarten@treewalker.org>,
mips-creator-ci20-dev@googlegroups.com,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paul.burton@mips.com>,
linux-mips@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Discussions about the Letux Kernel
<letux-kernel@openphoenux.org>
Subject: Re: MIPS: bug: gettimeofday syscall broken on CI20 board
Date: Thu, 28 Nov 2019 16:07:21 +0100 [thread overview]
Message-ID: <20191128150721.GA20142@alpha.franken.de> (raw)
In-Reply-To: <01D75E67-EC2E-4C74-B9BB-752773C481A9@goldelico.com>
On Thu, Nov 28, 2019 at 02:48:46PM +0100, H. Nikolaus Schaller wrote:
>
> What still does not fit into the picture is the errno = 1 i.e. EPERM.
> Maybe I have to study the libc code that tries to read the ELF symbols
> you have mentioned. It may fail for unknown reasons.
to understand vdso you might look at arch/mips/vdso and lib/vdso
kernel sources.
And if I understand it correctly you neither have a working high resolution
timer usable bei do_hres() in lib/vdso/gettimeofday.c or a working
gettimeofday_fallback(), which is enabled via CONFIG_MIPS_CLOCK_VSYSCALL
and needs either CSRC_R4K or CLKSRC_MIPS_GIC.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2019-11-28 15:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 16:21 MIPS: bug: gettimeofday syscall broken on CI20 board? H. Nikolaus Schaller
2019-11-17 13:14 ` MIPS: bug: gettimeofday syscall broken on CI20 board H. Nikolaus Schaller
2019-11-23 7:29 ` H. Nikolaus Schaller
2019-11-26 10:52 ` MIPS: " Vincenzo Frascino
2019-11-27 13:53 ` H. Nikolaus Schaller
2019-11-27 14:29 ` H. Nikolaus Schaller
2019-11-28 12:05 ` Vincenzo Frascino
2019-11-28 12:16 ` H. Nikolaus Schaller
2019-11-28 14:04 ` Vincenzo Frascino
2019-11-28 15:10 ` H. Nikolaus Schaller
2019-11-28 11:51 ` Vincenzo Frascino
2019-11-28 12:11 ` H. Nikolaus Schaller
2019-11-28 12:21 ` Vincenzo Frascino
2019-11-28 12:33 ` H. Nikolaus Schaller
2019-11-28 13:29 ` Maarten ter Huurne
2019-11-28 13:48 ` H. Nikolaus Schaller
2019-11-28 14:01 ` Vincenzo Frascino
2019-11-28 15:42 ` H. Nikolaus Schaller
2019-11-28 15:07 ` Thomas Bogendoerfer [this message]
2019-11-28 15:41 ` H. Nikolaus Schaller
2019-11-28 15:46 ` Vincenzo Frascino
2019-11-28 16:47 ` H. Nikolaus Schaller
2019-11-29 8:57 ` Vincenzo Frascino
2019-11-29 10:53 ` Vincenzo Frascino
2019-11-29 11:51 ` H. Nikolaus Schaller
2019-12-01 3:08 ` [PATCH] Mips32 gettimeofday fix kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191128150721.GA20142@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=hns@goldelico.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=maarten@treewalker.org \
--cc=mips-creator-ci20-dev@googlegroups.com \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.org \
--cc=vincenzo.frascino@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).