xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
* [Xen-devel] Ping²: [PATCH 1/2] core-parking: interact with runtime SMT-disabling
@ 2019-07-03 11:29 Jan Beulich
  2019-07-15  8:34 ` [Xen-devel] Ping³: " Jan Beulich
  0 siblings, 1 reply; 3+ messages in thread
From: Jan Beulich @ 2019-07-03 11:29 UTC (permalink / raw)
  To: Andrew Cooper
  Cc: Stefano Stabellini, Wei Liu, Konrad Wilk, George Dunlap,
	Tim Deegan, Julien Grall, Ian Jackson, xen-devel

>>> On 27.05.19 at 11:36,  wrote:
>>>> On 12.04.19 at 13:41,  wrote:
> >>>> On 11.04.19 at 21:06, <andrew.cooper3@citrix.com> wrote:
> > > On 11/04/2019 13:45, Jan Beulich wrote:
> > >> When disabling SMT at runtime, secondary threads should no longer be
> > >> candidates for bringing back up in response to _PUD ACPI events. Purge
> > >> them from the tracking array.
> > >>
> > >> Doing so involves adding locking to guard accounting data in the core
> > >> parking code. While adding the declaration for the lock take the liberty
> > >> to drop two unnecessary forward function declarations.
> > >>
> > >> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> > > 
> > > I can certainly appreciate these arguments, but surely the converse is
> > > true.  When SMT-enable is used, the newly-onlined threads are now
> > > eligible to be parked.
> > 
> > And nothing will keep them from getting parked.
> > 
> > > At the moment, this looks asymetric.
> > 
> > It does, but that's a result of core_parking.c only recording CPUs
> > it has parked, not ones it could park.
> 
> Did my responses address your concerns?
> 
> Jan
> 
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Xen-devel] Ping³: [PATCH 1/2] core-parking: interact with runtime SMT-disabling
  2019-07-03 11:29 [Xen-devel] Ping²: [PATCH 1/2] core-parking: interact with runtime SMT-disabling Jan Beulich
@ 2019-07-15  8:34 ` Jan Beulich
  0 siblings, 0 replies; 3+ messages in thread
From: Jan Beulich @ 2019-07-15  8:34 UTC (permalink / raw)
  To: Andrew Cooper
  Cc: Stefano Stabellini, Wei Liu, Konrad Wilk, George Dunlap,
	Tim Deegan, JulienGrall, xen-devel, Ian Jackson

On 03.07.2019 13:29, Jan Beulich wrote:
>>>> On 27.05.19 at 11:36,  wrote:
>>>>> On 12.04.19 at 13:41,  wrote:
>>>>>> On 11.04.19 at 21:06, <andrew.cooper3@citrix.com> wrote:
>>>> On 11/04/2019 13:45, Jan Beulich wrote:
>>>>> When disabling SMT at runtime, secondary threads should no longer be
>>>>> candidates for bringing back up in response to _PUD ACPI events. Purge
>>>>> them from the tracking array.
>>>>>
>>>>> Doing so involves adding locking to guard accounting data in the core
>>>>> parking code. While adding the declaration for the lock take the liberty
>>>>> to drop two unnecessary forward function declarations.
>>>>>
>>>>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>>>>
>>>> I can certainly appreciate these arguments, but surely the converse is
>>>> true.  When SMT-enable is used, the newly-onlined threads are now
>>>> eligible to be parked.
>>>
>>> And nothing will keep them from getting parked.
>>>
>>>> At the moment, this looks asymetric.
>>>
>>> It does, but that's a result of core_parking.c only recording CPUs
>>> it has parked, not ones it could park.
>>
>> Did my responses address your concerns?
>>
>> Jan

Ping?

Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Xen-devel] Ping: [PATCH 1/2] core-parking: interact with runtime SMT-disabling
  2019-05-27  9:36       ` Ping: " Jan Beulich
@ 2019-05-27  9:36         ` Jan Beulich
  0 siblings, 0 replies; 3+ messages in thread
From: Jan Beulich @ 2019-05-27  9:36 UTC (permalink / raw)
  To: Andrew Cooper
  Cc: Stefano Stabellini, Wei Liu, Konrad Rzeszutek Wilk,
	George Dunlap, Tim Deegan, Ian Jackson, Julien Grall, xen-devel

>>> On 12.04.19 at 13:41,  wrote:
>>>> On 11.04.19 at 21:06, <andrew.cooper3@citrix.com> wrote:
> > On 11/04/2019 13:45, Jan Beulich wrote:
> >> When disabling SMT at runtime, secondary threads should no longer be
> >> candidates for bringing back up in response to _PUD ACPI events. Purge
> >> them from the tracking array.
> >>
> >> Doing so involves adding locking to guard accounting data in the core
> >> parking code. While adding the declaration for the lock take the liberty
> >> to drop two unnecessary forward function declarations.
> >>
> >> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> > 
> > I can certainly appreciate these arguments, but surely the converse is
> > true.  When SMT-enable is used, the newly-onlined threads are now
> > eligible to be parked.
> 
> And nothing will keep them from getting parked.
> 
> > At the moment, this looks asymetric.
> 
> It does, but that's a result of core_parking.c only recording CPUs
> it has parked, not ones it could park.

Did my responses address your concerns?

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2019-07-15  8:54 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-03 11:29 [Xen-devel] Ping²: [PATCH 1/2] core-parking: interact with runtime SMT-disabling Jan Beulich
2019-07-15  8:34 ` [Xen-devel] Ping³: " Jan Beulich
  -- strict thread matches above, loose matches on Subject: below --
2019-04-11 12:04 [PATCH 0/2] core-parking: SMT-disable and section adjustments Jan Beulich
2019-04-11 12:45 ` [PATCH 1/2] core-parking: interact with runtime SMT-disabling Jan Beulich
2019-04-11 19:06   ` Andrew Cooper
2019-04-12 11:41     ` Jan Beulich
2019-05-27  9:36       ` Ping: " Jan Beulich
2019-05-27  9:36         ` [Xen-devel] " Jan Beulich

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