Re: [PATCH v2] arm64: paravirt: Use RCU read locks to guard stolen_time

2022-05-05 Thread Will Deacon
Hi Elliot, On Thu, Apr 28, 2022 at 11:35:36AM -0700, Elliot Berman wrote: > From: Prakruthi Deepak Heragu > > During hotplug, the stolen time data structure is unmapped and memset. > There is a possibility of the timer IRQ being triggered before memset > and stolen time is getting updated as

Re: [PATCH v2] arm64: paravirt: Use RCU read locks to guard stolen_time

2022-05-04 Thread Will Deacon
On Wed, May 04, 2022 at 03:38:47PM +0200, Juergen Gross wrote: > On 04.05.22 11:45, Will Deacon wrote: > > On Thu, Apr 28, 2022 at 11:35:36AM -0700, Elliot Berman wrote: > > > diff --git a/arch/arm64/kernel/paravirt.c b/arch/arm64/kernel/paravirt.c > > > index 75fed4460407..e724ea3d86f0 100644 > >

Re: [PATCH v2] arm64: paravirt: Use RCU read locks to guard stolen_time

2022-05-04 Thread Juergen Gross via Virtualization
On 28.04.22 20:35, Elliot Berman wrote: From: Prakruthi Deepak Heragu During hotplug, the stolen time data structure is unmapped and memset. There is a possibility of the timer IRQ being triggered before memset and stolen time is getting updated as part of this timer IRQ handler. This causes

Re: [PATCH v2] arm64: paravirt: Use RCU read locks to guard stolen_time

2022-05-04 Thread Juergen Gross via Virtualization
On 04.05.22 11:45, Will Deacon wrote: On Thu, Apr 28, 2022 at 11:35:36AM -0700, Elliot Berman wrote: From: Prakruthi Deepak Heragu During hotplug, the stolen time data structure is unmapped and memset. There is a possibility of the timer IRQ being triggered before memset and stolen time is

Re: [PATCH v2] arm64: paravirt: Use RCU read locks to guard stolen_time

2022-05-04 Thread Will Deacon
On Thu, Apr 28, 2022 at 11:35:36AM -0700, Elliot Berman wrote: > From: Prakruthi Deepak Heragu > > During hotplug, the stolen time data structure is unmapped and memset. > There is a possibility of the timer IRQ being triggered before memset > and stolen time is getting updated as part of this