* Waiman Long 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
* Waiman Long waiman.l...@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
On 08/14/2013 11:57 AM, Ingo Molnar wrote:
* Waiman Long wrote:
On 08/14/2013 06:20 AM, Ingo Molnar wrote:
* Waiman Long wrote:
I would like to share with you a rwlock related system crash that I
encountered during my testing with hackbench on an 80-core DL980. The
kernel crash because
On 08/14/2013 11:57 AM, Ingo Molnar wrote:
* Waiman Longwaiman.l...@hp.com wrote:
On 08/14/2013 06:20 AM, Ingo Molnar wrote:
* Waiman Longwaiman.l...@hp.com wrote:
I would like to share with you a rwlock related system crash that I
encountered during my testing with hackbench on an
* Waiman Long wrote:
> On 08/14/2013 06:20 AM, Ingo Molnar wrote:
> >* Waiman Long wrote:
> >
> >>
> >>I would like to share with you a rwlock related system crash that I
> >>encountered during my testing with hackbench on an 80-core DL980. The
> >>kernel crash because of a "watchdog detected
On 08/14/2013 06:20 AM, Ingo Molnar wrote:
* Waiman Long wrote:
I would like to share with you a rwlock related system crash that I
encountered during my testing with hackbench on an 80-core DL980. The
kernel crash because of a "watchdog detected hard lockup on cpu 79". The
crashing CPU was
* Waiman Long wrote:
> On 07/31/2013 08:00 PM, Waiman Long wrote:
> >v2->v3:
> > - Make read lock stealing the default and fair rwlock an option with
> >a different initializer.
> > - In queue_read_lock_slowpath(), check irq_count() and force spinning
> >and lock stealing in interrupt
* Waiman Long waiman.l...@hp.com wrote:
On 07/31/2013 08:00 PM, Waiman Long wrote:
v2-v3:
- Make read lock stealing the default and fair rwlock an option with
a different initializer.
- In queue_read_lock_slowpath(), check irq_count() and force spinning
and lock stealing in
On 08/14/2013 06:20 AM, Ingo Molnar wrote:
* Waiman Longwaiman.l...@hp.com wrote:
I would like to share with you a rwlock related system crash that I
encountered during my testing with hackbench on an 80-core DL980. The
kernel crash because of a watchdog detected hard lockup on cpu 79. The
* Waiman Long waiman.l...@hp.com wrote:
On 08/14/2013 06:20 AM, Ingo Molnar wrote:
* Waiman Longwaiman.l...@hp.com wrote:
I would like to share with you a rwlock related system crash that I
encountered during my testing with hackbench on an 80-core DL980. The
kernel crash because of a
On 07/31/2013 08:00 PM, Waiman Long wrote:
v2->v3:
- Make read lock stealing the default and fair rwlock an option with
a different initializer.
- In queue_read_lock_slowpath(), check irq_count() and force spinning
and lock stealing in interrupt context.
- Unify the fair and
On 07/31/2013 08:00 PM, Waiman Long wrote:
v2-v3:
- Make read lock stealing the default and fair rwlock an option with
a different initializer.
- In queue_read_lock_slowpath(), check irq_count() and force spinning
and lock stealing in interrupt context.
- Unify the fair and classic
v2->v3:
- Make read lock stealing the default and fair rwlock an option with
a different initializer.
- In queue_read_lock_slowpath(), check irq_count() and force spinning
and lock stealing in interrupt context.
- Unify the fair and classic read-side code path, and make write-side
to
v2-v3:
- Make read lock stealing the default and fair rwlock an option with
a different initializer.
- In queue_read_lock_slowpath(), check irq_count() and force spinning
and lock stealing in interrupt context.
- Unify the fair and classic read-side code path, and make write-side
to
14 matches
Mail list logo
