From: Rik van Riel <riel@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>, linux-kernel@vger.kernel.org
Cc: prarit@redhat.com, mgorman@suse.de, peterz@infradead.org,
alex.shi@intel.com, hpa@zytor.com
Subject: Re: deadlock between cpu_stopper & native_flush_tlb_others()->smp_call_function_many()
Date: Mon, 03 Mar 2014 11:45:04 -0500 [thread overview]
Message-ID: <5314B190.5060906@redhat.com> (raw)
In-Reply-To: <20140303174356.082ec348@nial.usersys.redhat.com>
On 03/03/2014 11:43 AM, Igor Mammedov wrote:
> It looks like I hit a deadlock between smp_call_function_many() and
> cpu_stopper threads.
> Are there any suggestions on how to fix this nicely?
This patch should fix it:
https://lkml.org/lkml/2014/2/28/194
next prev parent reply other threads:[~2014-03-03 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 16:43 deadlock between cpu_stopper & native_flush_tlb_others()->smp_call_function_many() Igor Mammedov
2014-03-03 16:45 ` Rik van Riel [this message]
2014-03-05 16:49 ` Igor Mammedov
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=5314B190.5060906@redhat.com \
--to=riel@redhat.com \
--cc=alex.shi@intel.com \
--cc=hpa@zytor.com \
--cc=imammedo@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=peterz@infradead.org \
--cc=prarit@redhat.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.