From: "Jan Beulich" <JBeulich@suse.com>
To: george.dunlap@citrix.com, Wei Liu <wei.liu2@citrix.com>,
Juergen Gross <jgross@suse.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Dario Faggioli <dario.faggioli@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
osstest service owner <osstest-admin@xenproject.org>,
Dario Faggioli <dfaggioli@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [xen-unstable test] 128240: regressions - FAIL
Date: Tue, 02 Oct 2018 02:29:44 -0600 [thread overview]
Message-ID: <5BB32C7802000078001ED8FA@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <ffd0c284-c1c9-680c-564a-ce066a1fb210@suse.com>
>>> On 01.10.18 at 18:07, <jgross@suse.com> wrote:
> On 01/10/2018 17:48, George Dunlap wrote:
>> On 10/01/2018 04:40 PM, Andrew Cooper wrote:
>>> If there isn't an obvious fix, then the switch of default scheduler
>>> needs reverting until there is a fix present. This is currently
>>> blocking master.
>>
>> Agreed. I'd argue for ignoring failures to set scheduler parameters on
>> migrate, on the grounds that this will be less risk to the project as a
>> whole than reverting credit2 again. But either way we should do
>> something quickly.
>
> We should ignore a mismatch of the scheduler. Failures when setting
> parameters for a matching scheduler should not be ignored IMO.
Well, depends on whether the scheduler was explicitly chosen.
I don't think migration should succeed when e.g. RTDS was used
and isn't available on the destination host.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-10-02 8:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-30 21:59 [xen-unstable test] 128240: regressions - FAIL osstest service owner
2018-10-01 9:04 ` Jan Beulich
2018-10-01 14:33 ` Wei Liu
2018-10-01 15:10 ` Jan Beulich
2018-10-01 15:17 ` Wei Liu
2018-10-01 15:19 ` George Dunlap
2018-10-01 15:35 ` Wei Liu
[not found] ` <fc2bbc89cfc7d9066fe0b1fd76ddd2ff@citrix.com>
[not found] ` <26110706a1830c111efd93ec76accd40@citrix.com>
[not found] ` <fc2bbc89„cfc7„d906„6fe0„b1fd76ddd2ff@citrix.com>
2018-10-01 15:40 ` Andrew Cooper
2018-10-01 15:48 ` George Dunlap
2018-10-01 16:07 ` Juergen Gross
2018-10-01 17:58 ` Dario Faggioli
2018-10-02 10:06 ` George Dunlap
2018-10-02 10:36 ` Dario Faggioli
2018-10-02 8:29 ` Jan Beulich [this message]
[not found] ` <5BB32C7802000078001ED8FA@suse.com>
2018-10-02 9:24 ` Dario Faggioli
2018-10-02 9:36 ` Jan Beulich
[not found] ` <5BB33C3202000078001ED99C@suse.com>
2018-10-02 9:58 ` Dario Faggioli
2018-10-01 18:02 ` Dario Faggioli
-- strict thread matches above, loose matches on Subject: below --
2018-10-02 8:45 Juergen Gross
[not found] <osstest128240mainreport@xen.org>
[not found] <osstest„128240„mainreport@xen.org>
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=5BB32C7802000078001ED8FA@prv1-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=dfaggioli@suse.com \
--cc=george.dunlap@citrix.com \
--cc=jgross@suse.com \
--cc=osstest-admin@xenproject.org \
--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.