[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YrsalGetwIfl8Wkw@zx2c4.com>
Date: Tue, 28 Jun 2022 17:13:24 +0200
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: "Alex Xu (Hello71)" <alex_y_xu@...oo.ca>
Cc: paulmck@...nel.org, rcu@...r.kernel.org, urezki@...il.com,
uladzislau.rezki@...y.com,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Arve Hjønnevåg <arve@...roid.com>,
Todd Kjos <tkjos@...roid.com>,
Martijn Coenen <maco@...roid.com>,
Joel Fernandes <joel@...lfernandes.org>,
Christian Brauner <christian@...uner.io>,
Hridya Valsaraju <hridya@...gle.com>,
Suren Baghdasaryan <surenb@...gle.com>,
linux-kernel@...r.kernel.org, wireguard@...ts.zx2c4.com,
Theodore Ts'o <tytso@....edu>, alexander.deucher@....com,
christian.koenig@....com, Xinhui.Pan@....com,
amd-gfx@...ts.freedesktop.org
Subject: Re: CONFIG_ANDROID (was: rcu_sched detected expedited stalls in
amdgpu after suspend)
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
Powered by blists - more mailing lists