mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Wang, Xiaoming" <xiaoming.wang@intel.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org, chuansheng.liu@intel.com
Subject: Re: [PATCH] lib/spinlock_debug: avoid one thread can not obtain the spinlock for a long time.
Date: Wed, 30 Apr 2014 08:06:25 +0200	[thread overview]
Message-ID: <20140430060625.GV11096@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1398877471.21870.6.camel@wxm-ubuntu>

On Wed, Apr 30, 2014 at 01:04:31PM -0400, Wang, Xiaoming wrote:
> loops_per_jiffy is larger than expectation that possible
> causes one thread can not obtain the spin lock for a long time.
> So use cpu_clock() to reach timeout in one second which can
> avoid HARD LOCKUP.

This is just not making sense.. one thing is broken so then you tape on
another? Fix the first already.

Also, why do you care?

  reply	other threads:[~2014-04-30  6:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30 17:04 Wang, Xiaoming
2014-04-30  6:06 ` Peter Zijlstra [this message]
2014-04-30  6:17   ` Wang, Xiaoming
2014-04-30  7:43     ` Peter Zijlstra

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=20140430060625.GV11096@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=chuansheng.liu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=xiaoming.wang@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
all inboxes | Powered by JetHome®