mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: Matt Rickard <matt@softrans.com.au>,
	Florian Weimer <fweimer@redhat.com>,
	Stephen Boyd <sboyd@kernel.org>,
	John Stultz <john.stultz@linaro.org>, X86 ML <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] x86/vdso: Handle clock_gettime(CLOCK_TAI) in vDSO
Date: Mon, 10 Sep 2018 12:38:07 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1809101235150.1402@nanos.tec.linutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1809092159440.1402@nanos.tec.linutronix.de>

On Sun, 9 Sep 2018, Thomas Gleixner wrote:
>  #ifdef BUILD_VDSO32_64
>  typedef u64 gtod_long_t;
>  #else
>  typedef unsigned long gtod_long_t;
>  #endif
> +
> +struct vgtod_ts {
> +	gtod_long_t	sec;

and actually this wants to become u64 unconditionally as we need to provide
the full seconds even on 32bit for the upcoming y2038 support. We still
have to truncate it for the current 32bit interface, but the core code
can be made ready now.

Thanks,

	tglx

  reply	other threads:[~2018-09-10 10:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-01  1:59 Matt Rickard
2018-09-01  3:39 ` Andy Lutomirski
2018-09-01  9:33   ` Florian Weimer
2018-09-01 17:37     ` Andy Lutomirski
2018-09-09 20:05   ` Thomas Gleixner
2018-09-10 10:38     ` Thomas Gleixner [this message]
2018-09-12 13:01     ` Florian Weimer
2018-09-12 14:17       ` Thomas Gleixner
2018-09-12 14:20         ` Florian Weimer
2018-09-12 14:29           ` Thomas Gleixner
2018-09-12 17:11             ` Andy Lutomirski
2018-09-13  8:07               ` Florian Weimer
2018-09-13 15:22                 ` Andy Lutomirski
2018-09-13 19:07                   ` Florian Weimer
2018-09-13 19:35                     ` Andy Lutomirski
2018-09-13 19:53                       ` Florian Weimer

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=alpine.DEB.2.21.1809101235150.1402@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=fweimer@redhat.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=matt@softrans.com.au \
    --cc=sboyd@kernel.org \
    --cc=x86@kernel.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
all inboxes | Powered by JetHome®