public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: linux-kernel@vger.kernel.org
Cc: John Stultz <john.stultz@linaro.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH 0/2] time: Fix races at clocksource switch time
Date: Wed, 14 Mar 2012 16:58:54 -0700	[thread overview]
Message-ID: <1331769536-4602-1-git-send-email-john.stultz@linaro.org> (raw)

In testing some recent timekeeping changes, I found some problem
when changing clocksources.

These two patches close races at clocksource switch time. One I sent out
earlier, and have reworked to integrate Thomas' comments.

These two patches, along with Thomas' recent cleanup patches ontop can
be found here:
	git://git.linaro.org/people/jstultz/linux.git fortglx/3.4/time

CC: Andy Lutomirski <luto@amacapital.net>
CC: Thomas Gleixner <tglx@linutronix.de>

John Stultz (2):
  time: x86: Fix race switching from vsyscall to non-vsyscall clock
  time: Fix change_clocksource locking

 arch/x86/vdso/vclock_gettime.c |   63 ++++++++++++++++++++++++----------------
 kernel/time/timekeeping.c      |    7 ++++
 2 files changed, 45 insertions(+), 25 deletions(-)

-- 
1.7.3.2.146.gca209


             reply	other threads:[~2012-03-14 23:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 23:58 John Stultz [this message]
2012-03-14 23:58 ` [PATCH 1/2] time: x86: Fix race switching from vsyscall to non-vsyscall clock John Stultz
2012-03-15  0:34   ` Thomas Gleixner
2012-03-15  0:42     ` John Stultz
2012-03-15  1:43       ` Andy Lutomirski
2012-03-15  1:46         ` Andy Lutomirski
2012-03-15 20:18         ` John Stultz
2012-03-15 21:01           ` Andy Lutomirski
2012-03-14 23:58 ` [PATCH 2/2] time: Fix change_clocksource locking 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=1331769536-4602-1-git-send-email-john.stultz@linaro.org \
    --to=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=tglx@linutronix.de \
    /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