From: Thomas Gleixner <tglx@linutronix.de>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: peterz@infradead.org, mingo@kernel.org,
akpm@linux-foundation.org, mgorman@techsingularity.net,
mhocko@kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: x86_64 Question: Are concurrent IPI requests safe?
Date: Wed, 11 May 2016 16:33:44 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1605111631430.3540@nanos> (raw)
In-Reply-To: <201605112309.AGJ18252.tOFMFQOJFLSOVH@I-love.SAKURA.ne.jp>
On Wed, 11 May 2016, Tetsuo Handa wrote:
> Peter Zijlstra wrote:
> > On Wed, May 11, 2016 at 10:19:16PM +0900, Tetsuo Handa wrote:
> > > [ 180.434659] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 07/31/2013
> >
> > can you reproduce on real hardware?
> >
> Unfortunately, I don't have a real hardware to run development kernels.
>
> My Linux environment is limited to 4 CPUs / 1024MB or 2048MB RAM running
> as a VMware guest on Windows. Can somebody try KVM environment with
> 4 CPUs / 1024MB or 2048MB RAM whith partition only plain /dev/sda1
> formatted as XFS?
Can you trigger a back trace on all cpus when the watchdog triggers?
Thanks,
tglx
next prev parent reply other threads:[~2016-05-11 14:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 10:58 [next-20160506 mm,smp] hang up at csd_lock_wait() from drain_all_pages() Tetsuo Handa
2016-05-09 14:54 ` x86_64 Question: Are concurrent IPI requests safe? Tetsuo Handa
2016-05-09 16:54 ` Thomas Gleixner
2016-05-11 13:19 ` Tetsuo Handa
2016-05-11 13:39 ` Peter Zijlstra
2016-05-11 14:09 ` Tetsuo Handa
2016-05-11 14:33 ` Thomas Gleixner [this message]
2016-05-11 15:19 ` Tetsuo Handa
2016-05-11 17:46 ` Peter Zijlstra
2016-05-11 21:56 ` Tetsuo Handa
2016-05-11 14:13 ` Thomas Gleixner
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=alpine.DEB.2.11.1605111631430.3540@nanos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=mingo@kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox