mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: John Stultz <john.stultz@linaro.org>,
	lkml <linux-kernel@vger.kernel.org>
Cc: John Stultz <john.stultz@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>,
	Miroslav Lichvar <mlichvar@redhat.com>,
	Richard Cochran <richardcochran@gmail.com>,
	Prarit Bhargava <prarit@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Paul Mackerras <paulus@samba.org>,
	Anton Blanchard <anton@samba.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Tony Luck <tony.luck@intel.com>,
	Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: [RFC][PATCH] time: Add warning about imminent deprecation of CONFIG_GENERIC_TIME_VSYSCALL_OLD
Date: Mon, 22 May 2017 10:58:50 +1000	[thread overview]
Message-ID: <87y3tpso51.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <1494613450-4713-1-git-send-email-john.stultz@linaro.org>

John Stultz <john.stultz@linaro.org> writes:

> CONFIG_GENERIC_TIME_VSYSCALL_OLD was introduced five years ago
> to allow a transition from the old vsyscall implementations to
> the new method (which simplified internal accounting and made
> timekeeping more precise).

I'm sure it's completely obvious to everyone except me what needs to be
done, but can you spell it out for me? Keeping in mind that I don't know
anything about the time keeping code.

> However, PPC and IA64 have yet to make the transition, despite
> in some cases me sending test patches to try to help it along.
>
> http://patches.linaro.org/patch/30501/
> http://patches.linaro.org/patch/35412/

I've never seen a PPC patch, did you send one?

> If its helpful, my last pass at the patches can be found here:
> https://git.linaro.org/people/john.stultz/linux.git dev/oldvsyscall-cleanup

Looks like it's just a draft for PPC. Do you think that should work and
it just needs testing? The comment about the vdso being "slightly
behind" is a little concerning.

cheers

  reply	other threads:[~2017-05-22  0:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12 18:24 John Stultz
2017-05-22  0:58 ` Michael Ellerman [this message]
2017-05-22 19:06   ` John Stultz
2017-05-22 20:45     ` Benjamin Herrenschmidt
2017-05-24 13:31     ` Michael Ellerman
2017-05-25 12:03     ` Paul Mackerras
2017-05-27  3:58       ` John Stultz

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=87y3tpso51.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=anton@samba.org \
    --cc=benh@kernel.crashing.org \
    --cc=fenghua.yu@intel.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mlichvar@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=paulus@samba.org \
    --cc=prarit@redhat.com \
    --cc=richardcochran@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.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

Powered by JetHome