Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Alex Xu (Hello71)" <>
	"Arve Hjønnevåg" <>,
	"Christian Brauner" <>,,
	"Greg Kroah-Hartman" <>,
	"Hridya Valsaraju" <>,
	"Jason A. Donenfeld" <>,
	"Joel Fernandes" <>,, "Martijn Coenen" <>,, "Suren Baghdasaryan" <>,
	"Todd Kjos" <>, "Theodore Ts'o" <>,,,,
Subject: Re: CONFIG_ANDROID (was: rcu_sched detected expedited stalls in amdgpu after suspend)
Date: Tue, 28 Jun 2022 15:28:26 -0400	[thread overview]
Message-ID: <1656443915.mdjoauhqe0.none@localhost> (raw)
In-Reply-To: <20220628185437.GA1790663@paulmck-ThinkPad-P17-Gen-1>

Excerpts from Paul E. McKenney's message of June 28, 2022 2:54 pm:
> All you need to do to get the previous behavior is to add something like
> this to your defconfig file:
> Any reason why this will not work for you?

As far as I know, I do not require any particular RCU debugging features 
intended for developers; as an individual user and distro maintainer, I 
would like to select the option corresponding to "emit errors for 
unexpected conditions which should be reported upstream", not "emit 
debugging information for development purposes".

Therefore, I think 0 is a suitable setting for me and most ordinary 
(not tightly controlled) distributions. My concern is that other users 
and distro maintainers will also have confusion about what value to set 
and whether the warnings are important, since the help text does not say 
anything about Android, and "make oldconfig" does not indicate that the 
default value is different for Android.

My suggestion is that the default be set to 0, and if a non-zero value 
is appropriate for Android, that should be communicated to the Android 
developers, not made conditional on CONFIG_ANDROID.


  reply	other threads:[~2022-06-28 19:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1656357116.rhe0mufk6a.none.ref@localhost>
     [not found] ` <1656357116.rhe0mufk6a.none@localhost>
     [not found]   ` <20220627204139.GL1790663@paulmck-ThinkPad-P17-Gen-1>
     [not found]     ` <1656379893.q9yb069erk.none@localhost>
     [not found]       ` <20220628041252.GV1790663@paulmck-ThinkPad-P17-Gen-1>
2022-06-28 15:02         ` Alex Xu (Hello71)
2022-06-28 15:13           ` Jason A. Donenfeld
2022-06-28 18:54           ` Paul E. McKenney
2022-06-28 19:28             ` Alex Xu (Hello71) [this message]
2022-06-28 20:11               ` Uladzislau Rezki
2022-07-04 11:30                 ` Christian König
2022-07-06 17:48                   ` Uladzislau Rezki
2022-07-06 17:58                     ` Paul E. McKenney
2022-07-06 18:09                       ` Uladzislau Rezki
2022-07-06 20:42                         ` Paul E. McKenney
2022-07-07  7:30                           ` Christian König
2022-07-07 13:29                             ` Paul E. McKenney

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1656443915.mdjoauhqe0.none@localhost \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).