All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Waiman Long <waiman.long@hp.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-arch@vger.kernel.org, x86@kernel.org,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Matt Fleming <matt.fleming@intel.com>,
	Michel Lespinasse <walken@google.com>,
	Andi Kleen <andi@firstfloor.org>, Rik van Riel <riel@redhat.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
	George Spelvin <linux@horizon.com>,
	Harvey Harrison <harvey.harrison@gmail.com>,
	"Chandramouleeswaran, Aswin" <aswin@hp.com>,
	"Norton, Scott J" <scott.norton@hp.com>
Subject: Re: [PATCH v3 0/3] qrwlock: Introducing a queue read/write lock implementation
Date: Mon, 19 Aug 2013 12:57:27 +0200	[thread overview]
Message-ID: <20130819105727.GA32308@gmail.com> (raw)
In-Reply-To: <520EAC07.5050106@hp.com>


* Waiman Long <waiman.long@hp.com> wrote:

> >Could be a CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE=1 
> >kernel?
> >
> >Thanks,
> >
> >	Ingo
> 
> My test system was a RHEL6.4 system. The 3.10 kernel 
> config file was based on the original RHEL6.4 config 
> file. So yes, the CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE 
> parameter was set.

Ok, good, so that's an expected panic.

Thanks,

	Ingo

      reply	other threads:[~2013-08-19 10:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01  0:00 [PATCH v3 0/3] qrwlock: Introducing a queue read/write lock implementation Waiman Long
2013-08-01  0:00 ` Waiman Long
2013-08-01  0:00 ` Waiman Long
2013-08-01  0:00 ` [PATCH v3 1/3] qrwlock: A " Waiman Long
2013-08-01  0:00   ` Waiman Long
2013-08-01  0:00   ` Waiman Long
2013-08-01  0:00 ` [PATCH v3 2/3] qrwlock x86: Enable x86 to use queue read/write lock Waiman Long
2013-08-01  0:00   ` Waiman Long
2013-08-01  0:00   ` Waiman Long
2013-08-01  0:00 ` [PATCH v3 3/3] qrwlock: Enable fair queue read/write lock behavior Waiman Long
2013-08-01  0:00   ` Waiman Long
2013-08-01  0:00   ` Waiman Long
2013-08-13 18:55 ` [PATCH v3 0/3] qrwlock: Introducing a queue read/write lock implementation Waiman Long
2013-08-14 10:20   ` Ingo Molnar
2013-08-14 15:23     ` Waiman Long
2013-08-14 15:57       ` Ingo Molnar
2013-08-16 22:47         ` Waiman Long
2013-08-19 10:57           ` Ingo Molnar [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=20130819105727.GA32308@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=arnd@arndb.de \
    --cc=aswin@hp.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=harvey.harrison@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.com \
    --cc=matt.fleming@intel.com \
    --cc=mingo@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=raghavendra.kt@linux.vnet.ibm.com \
    --cc=riel@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=scott.norton@hp.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=waiman.long@hp.com \
    --cc=walken@google.com \
    --cc=x86@kernel.org \
    /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.