From: John Stultz <johnstul@us.ibm.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
linux@openhuawei.org
Subject: Re: [PATCH 0/3][RFC] Fix for leapsecond caused futex issue (v4)
Date: Thu, 05 Jul 2012 09:27:16 -0700 [thread overview]
Message-ID: <4FF5C064.3040107@us.ibm.com> (raw)
In-Reply-To: <4FF5A79E.9030703@redhat.com>
On 07/05/2012 07:41 AM, Prarit Bhargava wrote:
> I tested this patchset for ~22 hours without any issues using my own leap second
> test code, John's previous leaptest.c and this new leap-a-day test with and
> without the -s option.
>
> In all x86 systems' cases (both AMD and Intel, large cpu count[1] and small cpu
> count) I also ran Firefox in the background and monitored it using top and
> occasionally breaking in to check the status of the futexes. I haven't seen
> anything wrong with any of the systems.
>
> John, my apologies for not getting to exactly 24 hours. I've usurped these
> systems long enough and other people need them :/. I'm going to continue to run
> two systems (one AMD and one Intel) for a longer stretch but I don't anticipate
> any issues at this point.
>
> So ...
>
> Acked-by: Prarit Bhargava <prarit@redhat.com>
>
> For the entire patchset.
Thanks so much! I greatly appreciate the extra testing and review you've
provided!
-john
prev parent reply other threads:[~2012-07-05 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 6:21 [PATCH 0/3][RFC] Fix for leapsecond caused futex issue (v4) John Stultz
2012-07-04 6:21 ` [PATCH 1/3] [RFC] hrtimer: Fix clock_was_set so it is safe to call from irq context John Stultz
2012-07-05 14:29 ` Prarit Bhargava
2012-07-04 6:21 ` [PATCH 2/3] [RFC] time: Fix leapsecond triggered hrtimer/futex load spike issue John Stultz
2012-07-05 14:29 ` Prarit Bhargava
2012-07-04 6:21 ` [PATCH 3/3] [RFC] hrtimer: Update hrtimer base offsets each hrtimer_interrupt John Stultz
2012-07-05 14:30 ` Prarit Bhargava
2012-07-04 6:23 ` [PATCH 0/3][RFC] Fix for leapsecond caused futex issue (v4) John Stultz
2012-07-05 14:41 ` Prarit Bhargava
2012-07-05 16:27 ` John Stultz [this message]
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=4FF5C064.3040107@us.ibm.com \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@openhuawei.org \
--cc=prarit@redhat.com \
--cc=stable@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.