All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Dimitri Sivanich <sivanich@sgi.com>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Gregory Haskins <ghaskins@novell.com>,
	Nick Piggin <npiggin@suse.de>, Tony Luck <tony.luck@gmail.com>,
	Robin Holt <holt@sgi.com>
Subject: Re: [PATCH] configure HAVE_UNSTABLE_SCHED_CLOCK for SGI_SN systems
Date: Thu, 22 Jan 2009 19:04:52 +0000	[thread overview]
Message-ID: <20090122190452.GA20770@kroah.com> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA35CD8C4C3@orsmsx505.amr.corp.intel.com>

On Thu, Jan 15, 2009 at 11:21:05AM -0800, Luck, Tony wrote:
> > > Greg, if everyone is OK with this patch, this should also be applied
> > > to all stable trees starting with 2.6.26.
> 
> > What is the status of this going into Linus's tree?
> 
> I'm about to ask Linus to pull a modified version that does
> a "select HAVE_UNSTABLE_SCHED_CLOCK" for all IA64 systems ...
> SGI sched_clock() is a lot less "stable" than most, but all
> ia64 systems can hit this as the ar.itc cycle counter is only
> s/w synchronized between cpus.

Thanks, I see it now and will queue it up for the next -stable releases.

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Dimitri Sivanich <sivanich@sgi.com>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Gregory Haskins <ghaskins@novell.com>,
	Nick Piggin <npiggin@suse.de>, Tony Luck <tony.luck@gmail.com>,
	Robin Holt <holt@sgi.com>
Subject: Re: [PATCH] configure HAVE_UNSTABLE_SCHED_CLOCK for SGI_SN systems
Date: Thu, 22 Jan 2009 11:04:52 -0800	[thread overview]
Message-ID: <20090122190452.GA20770@kroah.com> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA35CD8C4C3@orsmsx505.amr.corp.intel.com>

On Thu, Jan 15, 2009 at 11:21:05AM -0800, Luck, Tony wrote:
> > > Greg, if everyone is OK with this patch, this should also be applied
> > > to all stable trees starting with 2.6.26.
> 
> > What is the status of this going into Linus's tree?
> 
> I'm about to ask Linus to pull a modified version that does
> a "select HAVE_UNSTABLE_SCHED_CLOCK" for all IA64 systems ...
> SGI sched_clock() is a lot less "stable" than most, but all
> ia64 systems can hit this as the ar.itc cycle counter is only
> s/w synchronized between cpus.

Thanks, I see it now and will queue it up for the next -stable releases.

greg k-h

  reply	other threads:[~2009-01-22 19:04 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 16:27 [PATCH] configure HAVE_UNSTABLE_SCHED_CLOCK for SGI_SN systems Dimitri Sivanich
2009-01-06 16:27 ` Dimitri Sivanich
2009-01-06 17:12 ` Greg KH
2009-01-06 17:12   ` Greg KH
2009-01-06 20:15 ` Luck, Tony
2009-01-06 20:15   ` Luck, Tony
2009-01-06 20:19   ` Robin Holt
2009-01-06 20:19     ` Robin Holt
2009-01-06 20:34     ` Luck, Tony
2009-01-06 20:34       ` Luck, Tony
2009-01-06 20:57       ` Peter Zijlstra
2009-01-06 20:57         ` Peter Zijlstra
2009-01-06 22:50         ` Robin Holt
2009-01-06 22:50           ` Robin Holt
2009-01-06 23:16           ` Peter Zijlstra
2009-01-06 23:16             ` Peter Zijlstra
2009-01-07  3:00             ` Nick Piggin
2009-01-07  3:00               ` Nick Piggin
2009-01-07  3:16               ` Jack Steiner
2009-01-07  3:16                 ` Jack Steiner
2009-01-07  7:28               ` Peter Zijlstra
2009-01-07  7:28                 ` Peter Zijlstra
2009-01-07  7:40                 ` Nick Piggin
2009-01-07  7:40                   ` Nick Piggin
2009-01-07  9:43                 ` Robin Holt
2009-01-07  9:43                   ` Robin Holt
2009-01-07  9:53                   ` Peter Zijlstra
2009-01-07  9:53                     ` Peter Zijlstra
2009-01-07 13:32                     ` Dimitri Sivanich
2009-01-07 13:32                       ` Dimitri Sivanich
2009-01-07 15:16                       ` Peter Zijlstra
2009-01-07 15:16                         ` Peter Zijlstra
2009-01-15 18:48 ` Greg KH
2009-01-15 18:48   ` Greg KH
2009-01-15 19:21   ` Luck, Tony
2009-01-15 19:21     ` Luck, Tony
2009-01-22 19:04     ` Greg KH [this message]
2009-01-22 19:04       ` Greg KH

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=20090122190452.GA20770@kroah.com \
    --to=greg@kroah.com \
    --cc=ghaskins@novell.com \
    --cc=holt@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=peterz@infradead.org \
    --cc=sivanich@sgi.com \
    --cc=tony.luck@gmail.com \
    --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 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.