linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Zheng, Lv" <lv.zheng@intel.com>
To: Borislav Petkov <bp@alien8.de>, "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"stan.kain@gmail.com" <stan.kain@gmail.com>,
	"waffolz@hotmail.com" <waffolz@hotmail.com>,
	Josh Triplett <josh@joshtriplett.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	"mathieu.desnoyers@efficios.com" <mathieu.desnoyers@efficios.com>,
	"jiangshanlai@gmail.com" <jiangshanlai@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: RE: [PATCH] rcu: Narrow early boot window of illegal synchronous grace periods
Date: Mon, 16 Jan 2017 01:57:25 +0000	[thread overview]
Message-ID: <1AE640813FDE7649BE1B193DEA596E886CE2BD4E@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20170114125017.5wp2khn5scezeuau@pd.tnic>

Hi,

> From: Borislav Petkov [mailto:bp@alien8.de]
> Subject: Re: [PATCH] rcu: Narrow early boot window of illegal synchronous grace periods
> 
> On Sat, Jan 14, 2017 at 01:27:40PM +0100, Rafael J. Wysocki wrote:
> > OK, so this fixes the problem with synchronize_rcu_expedited() in
> > acpi_os_map_cleanup(), right?
> 
> Yeah.
> 
> > I wonder if the ACPI-specific fix is still needed, then?
> 
> It is not strictly necessary. If you still think it would be better to
> have it regardless, you could pick it up. I.e., making ACPI more robust,
> yadda yadda.
> 
> I dunno, though, perhaps it is only complicating the code unnecessarily
> and then can be safely ignored with a mental note for future freezes.

Glad to see it fixed inside of the API provider.

IMO, ACPI fix is unnecessary as ACPI is just a user of the RCU APIs.
And it's pointless to add special checks in the user side in order to use one of them.

Thanks and best regards
Lv

> 
> --
> Regards/Gruss,
>     Boris.
> 
> Good mailing practices for 400: avoid top-posting and trim the reply.

  reply	other threads:[~2017-01-16  1:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13  2:38 [PATCH] rcu: Narrow early boot window of illegal synchronous grace periods Paul E. McKenney
2017-01-13 11:25 ` Borislav Petkov
2017-01-14  8:00   ` Paul E. McKenney
2017-01-14 10:35     ` Borislav Petkov
2017-01-14 12:27       ` Rafael J. Wysocki
2017-01-14 12:50         ` Borislav Petkov
2017-01-16  1:57           ` Zheng, Lv [this message]
2017-01-16  4:56             ` Paul E. McKenney
2017-01-15  5:24       ` Paul E. McKenney
2017-01-15 10:09         ` Borislav Petkov
2017-01-15 20:33           ` Paul E. McKenney
2017-01-13 17:02 ` Borislav Petkov

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=1AE640813FDE7649BE1B193DEA596E886CE2BD4E@SHSMSX101.ccr.corp.intel.com \
    --to=lv.zheng@intel.com \
    --cc=bp@alien8.de \
    --cc=jiangshanlai@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rafael@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=stan.kain@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=waffolz@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).