From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
Cc: paulmck@kernel.org, rcu@vger.kernel.org, urezki@gmail.com,
uladzislau.rezki@sony.com,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Martijn Coenen" <maco@android.com>,
"Joel Fernandes" <joel@joelfernandes.org>,
"Christian Brauner" <christian@brauner.io>,
"Hridya Valsaraju" <hridya@google.com>,
"Suren Baghdasaryan" <surenb@google.com>,
linux-kernel@vger.kernel.org, wireguard@lists.zx2c4.com,
"Theodore Ts'o" <tytso@mit.edu>,
alexander.deucher@amd.com, christian.koenig@amd.com,
Xinhui.Pan@amd.com, amd-gfx@lists.freedesktop.org
Subject: Re: CONFIG_ANDROID (was: rcu_sched detected expedited stalls in amdgpu after suspend)
Date: Tue, 28 Jun 2022 17:13:24 +0200 [thread overview]
Message-ID: <YrsalGetwIfl8Wkw@zx2c4.com> (raw)
In-Reply-To: <1656421946.ic03168yc3.none@localhost>
Hi Alex,
On Tue, Jun 28, 2022 at 11:02:40AM -0400, Alex Xu (Hello71) wrote:
> WireGuard and random also use CONFIG_ANDROID in a similar "proxy" way as
> rcu, there to see if suspends are "frequent". This seems dubious for the
> same reasons.
I'd be happy to take a patch in WireGuard and random.c to get rid of the
CONFIG_ANDROID usage, if you can conduct an analysis and conclude this
won't break anything inadvertently.
Jason
next prev parent reply other threads:[~2022-06-28 15:13 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 [this message]
2022-06-28 18:54 ` Paul E. McKenney
2022-06-28 19:28 ` Alex Xu (Hello71)
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:
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=YrsalGetwIfl8Wkw@zx2c4.com \
--to=jason@zx2c4.com \
--cc=Xinhui.Pan@amd.com \
--cc=alex_y_xu@yahoo.ca \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=arve@android.com \
--cc=christian.koenig@amd.com \
--cc=christian@brauner.io \
--cc=gregkh@linuxfoundation.org \
--cc=hridya@google.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=surenb@google.com \
--cc=tkjos@android.com \
--cc=tytso@mit.edu \
--cc=uladzislau.rezki@sony.com \
--cc=urezki@gmail.com \
--cc=wireguard@lists.zx2c4.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).