From: Frank Rowand <frank.rowand@am.sony.com>
To: "Rowand, Frank" <Frank_Rowand@sonyusa.com>
Cc: Aaditya Kumar <aaditya.kumar.30@gmail.com>,
"shaohua.li@intel.com" <shaohua.li@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"mingo@kernel.org" <mingo@kernel.org>,
"C.Emde@osadl.org" <C.Emde@osadl.org>,
"jkacur@redhat.com" <jkacur@redhat.com>,
"Bird, Tim" <Tim.Bird@am.sony.com>,
"Ohara, Takuzo" <Takuzo.Ohara@ap.sony.com>,
"Iibuchi, Kan (TDG)" <Kan.Iibuchi@jp.sony.com>
Subject: Re: [RFC][RT][PATCH] mm: Do not use stop_machine() for __zone_pcp_udpate() for CONFIG_PREEMPT_RT_FULL
Date: Tue, 19 Jun 2012 14:52:51 -0700 [thread overview]
Message-ID: <4FE0F4B3.5090705@am.sony.com> (raw)
In-Reply-To: <4FE0D70F.2000607@am.sony.com>
On 06/19/12 12:46, Frank Rowand wrote:
> Adding to the distribution list: the author of the patch that included
> the call to stop_machine() (commit 112067f0905b2de862c607ee62411cf47d2fe5c4).
>
> On 06/19/12 11:32, Aaditya Kumar wrote:
>> The code path of __zone_pcp_update() has following locks, which in
>> CONFIG_PREEMPT_RT_FULL=y are rt-mutex.
>> - pa_lock locked by cpu_lock_irqsave()
>> - zone->lock locked by free_pcppages_bulk()
>>
>> Since __zone_pcp_update() is called from stop_machine(), so with
< snip >
... and just for the record, adding the author (Shaohua Li) did not
work, I got an email reject from Intel.
-Frank
next prev parent reply other threads:[~2012-06-19 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 18:32 [RFC][RT][PATCH] mm: Do not use stop_machine() for __zone_pcp_udpate() for CONFIG_PREEMPT_RT_FULL Aaditya Kumar
2012-06-19 19:46 ` Frank Rowand
2012-06-19 21:52 ` Frank Rowand [this message]
2012-06-23 3:37 ` KOSAKI Motohiro
2012-06-24 16:55 ` Aaditya Kumar
2012-06-25 8:00 ` Aaditya Kumar
2012-06-25 8:00 ` Aaditya Kumar
2013-03-05 18:40 ` [RFC][RT][PATCH RESEND] " Aaditya Kumar
2013-03-05 19:21 ` Steven Rostedt
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=4FE0F4B3.5090705@am.sony.com \
--to=frank.rowand@am.sony.com \
--cc=C.Emde@osadl.org \
--cc=Frank_Rowand@sonyusa.com \
--cc=Kan.Iibuchi@jp.sony.com \
--cc=Takuzo.Ohara@ap.sony.com \
--cc=Tim.Bird@am.sony.com \
--cc=aaditya.kumar.30@gmail.com \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shaohua.li@intel.com \
--cc=tglx@linutronix.de \
/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.