Re: CONFIG_ANDROID (was: rcu_sched detected expedited stalls in amdgpu after suspend)

2022-07-07 Thread Paul E. McKenney
On Thu, Jul 07, 2022 at 09:30:39AM +0200, Christian König wrote: > Am 06.07.22 um 22:42 schrieb Paul E. McKenney: > > On Wed, Jul 06, 2022 at 08:09:49PM +0200, Uladzislau Rezki wrote: > > > On Wed, Jul 06, 2022 at 10:58:36AM -0700, Paul E. McKenney wrote: > > > > On Wed, Jul 06, 2022 at 07:48:20PM

Re: CONFIG_ANDROID (was: rcu_sched detected expedited stalls in amdgpu after suspend)

2022-07-07 Thread Christian König
Am 06.07.22 um 22:42 schrieb Paul E. McKenney: On Wed, Jul 06, 2022 at 08:09:49PM +0200, Uladzislau Rezki wrote: On Wed, Jul 06, 2022 at 10:58:36AM -0700, Paul E. McKenney wrote: On Wed, Jul 06, 2022 at 07:48:20PM +0200, Uladzislau Rezki wrote: Hello. On Mon, Jul 04, 2022 at 01:30:50PM +0200,

Re: CONFIG_ANDROID (was: rcu_sched detected expedited stalls in amdgpu after suspend)

2022-07-06 Thread Paul E. McKenney
On Wed, Jul 06, 2022 at 08:09:49PM +0200, Uladzislau Rezki wrote: > On Wed, Jul 06, 2022 at 10:58:36AM -0700, Paul E. McKenney wrote: > > On Wed, Jul 06, 2022 at 07:48:20PM +0200, Uladzislau Rezki wrote: > > > Hello. > > > > > > On Mon, Jul 04, 2022 at 01:30:50PM +0200, Christian König wrote: > >

Re: CONFIG_ANDROID (was: rcu_sched detected expedited stalls in amdgpu after suspend)

2022-07-06 Thread Uladzislau Rezki
On Wed, Jul 06, 2022 at 10:58:36AM -0700, Paul E. McKenney wrote: > On Wed, Jul 06, 2022 at 07:48:20PM +0200, Uladzislau Rezki wrote: > > Hello. > > > > On Mon, Jul 04, 2022 at 01:30:50PM +0200, Christian König wrote: > > > Hi guys, > > > > > > Am 28.06.22 um 22:11 schrieb Uladzislau Rezki: > > >

Re: CONFIG_ANDROID (was: rcu_sched detected expedited stalls in amdgpu after suspend)

2022-07-06 Thread Paul E. McKenney
On Wed, Jul 06, 2022 at 07:48:20PM +0200, Uladzislau Rezki wrote: > Hello. > > On Mon, Jul 04, 2022 at 01:30:50PM +0200, Christian König wrote: > > Hi guys, > > > > Am 28.06.22 um 22:11 schrieb Uladzislau Rezki: > > > > Excerpts from Paul E. McKenney's message of June 28, 2022 2:54 pm: > > > > >

Re: CONFIG_ANDROID (was: rcu_sched detected expedited stalls in amdgpu after suspend)

2022-07-06 Thread Uladzislau Rezki
Hello. On Mon, Jul 04, 2022 at 01:30:50PM +0200, Christian König wrote: > Hi guys, > > Am 28.06.22 um 22:11 schrieb Uladzislau Rezki: > > > 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 > > > > t

Re: CONFIG_ANDROID (was: rcu_sched detected expedited stalls in amdgpu after suspend)

2022-07-04 Thread Christian König
Hi guys, Am 28.06.22 um 22:11 schrieb Uladzislau Rezki: 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: CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=21000 Any reason why this will not

Re: CONFIG_ANDROID

2022-06-30 Thread Jason A. Donenfeld
On Thu, Jun 30, 2022 at 5:53 PM tlhackque wrote: > If you also want to make sure that the key isn't in memory longer than > that time (e.g. to avoid capture on a dump or device loss), you could > also set a timer (of the sort that wakes the CPU from sleep) that clears > the key at that time. Waki

Re: CONFIG_ANDROID

2022-06-30 Thread tlhackque
On 30-Jun-22 07:41, Jason A. Donenfeld wrote: On Thu, Jun 30, 2022 at 06:47:38AM -0400, tlhackque wrote: FWIW: Having watched the discussion about CONFIG_ANDROID, it occurs to me that there's an alternative for WireGuard that sidesteps the issue. From the last patcheset, it seems that the onl

Re: CONFIG_ANDROID

2022-06-30 Thread Jason A. Donenfeld
On Thu, Jun 30, 2022 at 06:47:38AM -0400, tlhackque wrote: > FWIW: Having watched the discussion about CONFIG_ANDROID, it occurs to > me that there's an alternative for WireGuard that sidesteps the issue. > > From the last patcheset, it seems that the only use in WireGuard is to > avoid clearin

Re: CONFIG_ANDROID (was: rcu_sched detected expedited stalls in amdgpu after suspend)

2022-06-29 Thread Uladzislau Rezki
> 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: > > > > CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=21000 > > > > Any reason why this will not work for you? > > As far as I kno

Re: CONFIG_ANDROID (was: rcu_sched detected expedited stalls in amdgpu after suspend)

2022-06-28 Thread Alex Xu (Hello71)
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: > > CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=21000 > > Any reason why this will not work for you? As far as I know, I do not requir

Re: CONFIG_ANDROID (was: rcu_sched detected expedited stalls in amdgpu after suspend)

2022-06-28 Thread Paul E. McKenney
On Tue, Jun 28, 2022 at 11:02:40AM -0400, Alex Xu (Hello71) wrote: > Excerpts from Paul E. McKenney's message of June 28, 2022 12:12 am: > > On Mon, Jun 27, 2022 at 09:50:53PM -0400, Alex Xu (Hello71) wrote: > >> Ah, I see. I have selected the default value for > >> CONFIG_RCU_EXP_CPU_STALL_TIMEOU

Re: CONFIG_ANDROID (was: rcu_sched detected expedited stalls in amdgpu after suspend)

2022-06-28 Thread Jason A. Donenfeld
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.