[ Late reply, due to Plumbers followed by a much needed vacation and then drowning in 3 weeks of unread email! ]
On Fri, 21 Aug 2020 17:35:32 +0200 Marco Elver <el...@google.com> wrote: > So, if the _rcuidle() variant here doesn't break your usecase, there > should be no harm in using the _rcuidle() variant. This also lifts the > restriction on where prandom_u32() is usable to what it was before, > which should be any context. > > Steven, Peter: What's the downside to of _rcuidle()? _rcuidle() only has a slightly more overhead in the tracing path (it's no different when not tracing). There's not a issue with _rcuidle() itself. The issue is that we need to have it. We'd like it to be that rcu *is* watching always except for a very minimal locations when switching context (kernel to and from user and running to and from idle), and then we just don't let tracing or anything that needs rcu in those locations. But for your patch: Acked-by: Steven Rostedt (VMware) <rost...@goodmis.org> -- Steve
