This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC PATCH] AARCH64/ILP32: introduce kernel time types
- From: Yury Norov <ynorov at caviumnetworks dot com>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: <libc-alpha at sourceware dot org>, <arnd at arndb dot de>, <vapier at gentoo dot org>, <joseph at codesourcery dot com>, <cmetcalf at tilera dot com>, <pinskia at gmail dot com>, <cmetcalf at mellanox dot com>, <szabolcs dot nagy at arm dot com>, <bamvor dot zhangjian at huawei dot com>, <catalin dot marinas at arm dot com>, <fweimer at redhat dot com>, <Prasun dot Kapoor at cavium dot com>, <maxim dot kuvyrkov at linaro dot org>
- Date: Tue, 28 Jun 2016 13:58:23 +0300
- Subject: Re: [RFC PATCH] AARCH64/ILP32: introduce kernel time types
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp dot mailfrom=Yuri dot Norov at caviumnetworks dot com;
- References: <1467103498-24243-1-git-send-email-ynorov at caviumnetworks dot com> <mvmshvxk4n6 dot fsf at hawking dot suse dot de> <20160628102000 dot GA24779 at yury-N73SV> <mvmk2h9k3qh dot fsf at hawking dot suse dot de>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
On Tue, Jun 28, 2016 at 12:27:34PM +0200, Andreas Schwab wrote:
> Yury Norov <ynorov@caviumnetworks.com> writes:
>
> > Utmp does not deal with kernel, that's true. But this is time types by
> > nature, and native ABI keeps it synced with kernel. And ILP ABI has to
> > be compatible with navive ABI, and so has to have it synced with
> > kernel as well.
>
> Since it is an on-disk format it needs to be handled specially, to avoid
> the difficulties we have now on aarch64 to resurface for future ports.
>
> Andreas.
I still think this is correct way. We have single, kernel-synced type
for communicating with kernel and native ABI (disk), and convert it to
user type where needed (currently for aarch64/stat only). It also
helps to move to 64-bit time types smoothly, as we can make time_t
deprecated and force new APIs use __ktime_t.
What sort of difficulties you see with this approach?
Yury.