From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] S390: Fix backtrace in vdso functions.
Date: Tue, 28 Nov 2017 16:35:00 -0000 [thread overview]
Message-ID: <2398b595-b329-8805-9948-d2e090e13f6f@linaro.org> (raw)
In-Reply-To: <163688cc-95d7-e7f1-6d52-67dd3d20b82a@linaro.org>
On 28/11/2017 13:53, Adhemerval Zanella wrote:
>
>
> On 28/11/2017 12:18, Florian Weimer wrote:
>> On 11/28/2017 02:09 PM, Adhemerval Zanella wrote:
>>> I am almost sure we can remove it for powerpc as well (I can't see
>>> no immediate gain on doing a function call using inline assembly
>>> as for INTERNAL_VSYSCALL_NO_SYSCALL_FALLBACK on powerpc).
>>
>> Is there another way to obtain the condition code for the error status?
>>
>>  /* The vDSO does not return an error (it clear cr0.so on returning). */
>> Â INTERNAL_SYSCALL_DECL (err);
>> Â result =
>> Â Â Â INTERNAL_VSYSCALL_NO_SYSCALL_FALLBACK (get_tbfreq, err, uint64_t, 0);
>>
>> Thanks,
>> Florian
>
> I think we can simplify this call in specific since __kernel_get_tbfreq
> always succeed if the vDSO is present. The only issue is the symbol
> returns an uint64_t even for powerpc32.
>
The problem is for __kernel_clock_getres and __kernel_clock_gettime the
fallback for clocks different than CLOCK_REALTIME or CLOCK_MONOTONIC
is to issue a syscall (and then it requires a mfcr to get the result
value).
next prev parent reply other threads:[~2017-11-28 16:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 12:44 Stefan Liebler
2017-11-28 13:09 ` Adhemerval Zanella
2017-11-28 14:18 ` Florian Weimer
2017-11-28 15:53 ` Adhemerval Zanella
2017-11-28 16:35 ` Adhemerval Zanella [this message]
2017-12-04 8:00 ` Stefan Liebler
2017-12-04 10:48 ` Adhemerval Zanella
2017-12-04 15:42 ` Stefan Liebler
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=2398b595-b329-8805-9948-d2e090e13f6f@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).