public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Ben Greear <greearb@candelatech.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Willy Tarreau <w@1wt.eu>
Subject: [GIT PULL] RTC fixes for 3.1
Date: Mon, 25 Jul 2011 23:29:54 -0700	[thread overview]
Message-ID: <1311661794.2945.305.camel@work-vm> (raw)

Hey Thomas,
	So while your analysis obviously pointed out the problem, just to be
sure I took your rtc patches and ran them through the stress test that I
was using to reproduce the issue Ben reported, and they've lasted for
over six hours now without issue (usually I could trigger the lockup in
30 minutes to an hour).

Thanks again for the narrowing down the issue and the patches to fix it!

I've reworked some of the commit logs and also refined the PIE hrtimer
freq limit (using Willy's suggestion of the ~8khz max value from the man
page). The patches are available in the git repository at:

  git://git.linaro.org/people/jstultz/linux.git fortglx/3.1/tip/timers/rtc

Thomas Gleixner (3):
      rtc: Handle errors correctly in rtc_irq_set_state()
      rtc: Fix hrtimer deadlock
      rtc: Limit RTC PIE frequency

 drivers/rtc/interface.c |   55 ++++++++++++++++++++++++++++++++--------------
 include/linux/rtc.h     |    3 ++
 2 files changed, 41 insertions(+), 17 deletions(-)



             reply	other threads:[~2011-07-26  6:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26  6:29 john stultz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-08-27  0:36 [GIT PULL] RTC fixes for 3.1 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=1311661794.2945.305.camel@work-vm \
    --to=johnstul@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=w@1wt.eu \
    /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