From: "Jan Beulich" <JBeulich@suse.com>
To: Juergen Gross <jgross@suse.com>, FionaLi-oc <fionali-oc@zhaoxin.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
cobechen@zhaoxin.com, Dario Faggioli <dfaggioli@suse.com>
Subject: Re: [PATCH] cpupool: fix ASSERT( c != old_pool )
Date: Mon, 08 Apr 2019 03:26:50 -0600 [thread overview]
Message-ID: <5CAB13DA02000078002253F7@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <31983788-e4e4-5526-04a1-660c00930d0d@suse.com>
>>> On 08.04.19 at 07:09, <jgross@suse.com> wrote:
> On 08/04/2019 04:40, FionaLi-oc wrote:
>> Assigning cpu to cpupool needn't to switch cpu scheduler when
>> system state is resume, otherwise it will cause ASSERT in
>> schedule_cpu_switch().
>
> I don't think this patch is needed on current staging tree. Commit
> 6870ea9d1fad6fbe27 changed resume handling leading to
> cpupool_assign_cpu_locked() being no longer called when resuming.
But is it something worthwhile to put onto stable trees (with the
one missing blank added)?
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Jan Beulich" <JBeulich@suse.com>
To: "Juergen Gross" <jgross@suse.com>, "FionaLi-oc" <fionali-oc@zhaoxin.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
cobechen@zhaoxin.com, Dario Faggioli <dfaggioli@suse.com>
Subject: Re: [Xen-devel] [PATCH] cpupool: fix ASSERT( c != old_pool )
Date: Mon, 08 Apr 2019 03:26:50 -0600 [thread overview]
Message-ID: <5CAB13DA02000078002253F7@prv1-mh.provo.novell.com> (raw)
Message-ID: <20190408092650.fEU49qNgMp8Pu8now9WGQ3MZC4mXgOxFkj0BUgR6hEM@z> (raw)
In-Reply-To: <31983788-e4e4-5526-04a1-660c00930d0d@suse.com>
>>> On 08.04.19 at 07:09, <jgross@suse.com> wrote:
> On 08/04/2019 04:40, FionaLi-oc wrote:
>> Assigning cpu to cpupool needn't to switch cpu scheduler when
>> system state is resume, otherwise it will cause ASSERT in
>> schedule_cpu_switch().
>
> I don't think this patch is needed on current staging tree. Commit
> 6870ea9d1fad6fbe27 changed resume handling leading to
> cpupool_assign_cpu_locked() being no longer called when resuming.
But is it something worthwhile to put onto stable trees (with the
one missing blank added)?
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-04-08 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 2:40 [PATCH] cpupool: fix ASSERT( c != old_pool ) FionaLi-oc
2019-04-08 2:40 ` [Xen-devel] " FionaLi-oc
2019-04-08 5:09 ` Juergen Gross
2019-04-08 5:09 ` [Xen-devel] " Juergen Gross
2019-04-08 9:26 ` Jan Beulich [this message]
2019-04-08 9:26 ` Jan Beulich
2019-04-08 10:25 Juergen Gross
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=5CAB13DA02000078002253F7@prv1-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=cobechen@zhaoxin.com \
--cc=dfaggioli@suse.com \
--cc=fionali-oc@zhaoxin.com \
--cc=jgross@suse.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.