All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Dario Faggioli <dfaggioli@suse.com>, xen-devel@lists.xenproject.org
Cc: "George Dunlap" <george.dunlap@eu.citrix.com>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Wei Liu" <wei.liu2@citrix.com>,
	"Jan Beulich" <jbeulich@suse.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH 1/6] xen/sched: call cpu_disable_scheduler() via cpu notifier
Date: Wed, 27 Mar 2019 17:53:46 +0100	[thread overview]
Message-ID: <6b1cfffb-02ae-4859-94aa-29676b0c18da@suse.com> (raw)
In-Reply-To: <4585c758d5e6928acf5ed714ad5f13bf3991492f.camel@suse.com>

On 27/03/2019 17:51, Dario Faggioli wrote:
> On Wed, 2019-03-27 at 17:31 +0100, Juergen Gross wrote:
>> On 27/03/2019 17:24, Dario Faggioli wrote:
>>> On Mon, 2019-03-18 at 14:11 +0100, Juergen Gross wrote:
>>>> cpu_disable_scheduler() is being called from __cpu_disable()
>>>> today.
>>>> There is no need to call it on the cpu just being disabled, so
>>>> use
>>>> the CPU_DEAD case of the cpu notifier chain.
>>>>
>>> So, what do you mean with "There is no need to call it on the cpu
>>> just
>>> being disabled"?
>>>
>>> Because we still (even after this patch, I mean) call
>>> cpu_disable_scheduler() on all non-boot CPUs, aren't we? It's just
>>> that
>>> right now we call it from __cpu_disable(), with the patch we call
>>> it
>>> slightly later.
>>
>> The CPU_DEAD notifier chain is called on the CPU requesting the other
>> one to go down (so on the boot CPU in suspend case). So we call it
>> _for_
>> all non-boot CPUs in the boot CPU.
>>
> Mmm... ok, I see what you mean now.
> 
> I guess part of "the problem" is that "call func on cpu A" reads, at
> least to me, as both 1) call func so that it acts on and change the
> state of cpu A, and 2) call func in such a way that it executes on cpu
> A.

I'll rephrase to "execute func on cpu...".


Juergen


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

  reply	other threads:[~2019-03-27 16:53 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 13:11 [PATCH 0/6] xen: simplify suspend/resume handling Juergen Gross
2019-03-18 13:11 ` [PATCH 1/6] xen/sched: call cpu_disable_scheduler() via cpu notifier Juergen Gross
2019-03-27 15:34   ` Andrew Cooper
2019-03-27 15:35   ` George Dunlap
2019-03-27 16:22   ` Jan Beulich
2019-03-27 16:24   ` Dario Faggioli
2019-03-27 16:31     ` Juergen Gross
2019-03-27 16:51       ` Dario Faggioli
2019-03-27 16:53         ` Juergen Gross [this message]
     [not found]   ` <5C9BA336020000780022235B@suse.com>
2019-03-27 16:45     ` Juergen Gross
2019-03-27 16:58       ` Jan Beulich
2019-03-18 13:11 ` [PATCH 2/6] xen: add helper for calling notifier_call_chain() to common/cpu.c Juergen Gross
2019-03-25 11:56   ` Dario Faggioli
2019-03-27 12:25   ` George Dunlap
2019-03-27 15:39   ` Andrew Cooper
2019-03-27 16:05     ` Juergen Gross
2019-03-18 13:11 ` [PATCH 3/6] xen: add new cpu notifier action CPU_RESUME_FAILED Juergen Gross
2019-03-25 12:21   ` Dario Faggioli
2019-03-25 12:29     ` Juergen Gross
2019-03-27 15:54       ` Dario Faggioli
2019-03-27 15:49   ` George Dunlap
2019-03-27 16:29   ` Jan Beulich
     [not found]   ` <5C9BA5010200007800222375@suse.com>
2019-03-27 16:32     ` Juergen Gross
2019-03-18 13:11 ` [PATCH 4/6] xen: don't free percpu areas during suspend Juergen Gross
2019-03-25 18:14   ` Dario Faggioli
2019-03-27 15:55   ` Andrew Cooper
2019-03-27 16:18     ` Juergen Gross
2019-03-27 16:38       ` Jan Beulich
     [not found]       ` <5C9BA70E02000078002223A3@suse.com>
2019-03-27 16:52         ` Juergen Gross
2019-03-28  6:59           ` Juergen Gross
2019-03-28  8:03             ` Jan Beulich
2019-04-11  9:49               ` Jan Beulich
2019-04-11  9:49                 ` [Xen-devel] " Jan Beulich
     [not found]             ` <5C9C7FD202000078002225AB@suse.com>
2019-03-28  8:35               ` Juergen Gross
2019-03-28  9:36                 ` Jan Beulich
2019-03-28  7:46   ` Jan Beulich
     [not found]   ` <5C9C7BF1020000780022258F@suse.com>
2019-03-28  7:53     ` Juergen Gross
2019-03-28  8:04       ` Jan Beulich
2019-03-18 13:11 ` [PATCH 5/6] xen/cpupool: simplify suspend/resume handling Juergen Gross
2019-03-27 15:56   ` George Dunlap
2019-03-27 16:32   ` Dario Faggioli
2019-03-18 13:11 ` [PATCH 6/6] xen/sched: don't disable scheduler on cpus during suspend Juergen Gross
2019-03-27 23:10   ` Dario Faggioli
2019-03-28  5:41     ` Juergen Gross
  -- strict thread matches above, loose matches on Subject: below --
2019-03-27 17:06 [PATCH 1/6] xen/sched: call cpu_disable_scheduler() via cpu notifier Juergen Gross
2019-03-27 23:05 ` Dario Faggioli
     [not found] <20190318131155.29450*1*jgross@suse.com>
     [not found] ` <20190318131155.29450*5*jgross@suse.com>
     [not found] <20190318131155.29450****1****jgross@suse.com>
     [not found] ` <20190318131155.29450****5****jgross@suse.com>
     [not found]   ` <e10c14cd****54ac****8d8c****2d5c****db4adbd39d07@citrix.com>

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=6b1cfffb-02ae-4859-94aa-29676b0c18da@suse.com \
    --to=jgross@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=dfaggioli@suse.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=roger.pau@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.