From: Dario Faggioli <dfaggioli@suse.com>
To: George Dunlap <george.dunlap@citrix.com>,
Juergen Gross <jgross@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xenproject.org
Cc: Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Tim Deegan <tim@xen.org>, Jan Beulich <jbeulich@suse.com>,
Ian Jackson <ian.jackson@citrix.com>
Subject: Re: [PATCH 1/3] Make credit2 the default scheduler
Date: Tue, 06 Feb 2018 23:39:54 +0100 [thread overview]
Message-ID: <1517956794.4823.27.camel@suse.com> (raw)
In-Reply-To: <64cddb91-57ca-45ae-2308-f4f844248d5e@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1188 bytes --]
On Tue, 2018-02-06 at 17:02 +0000, George Dunlap wrote:
> On 02/06/2018 06:18 AM, Juergen Gross wrote:
> > On 05/02/18 17:53, Dario Faggioli wrote:
> > >
> > > Considering we're releasing in June, but freezing in March, do we
> > > think
> > > it is still early enough?
>
> > The 4.11 release is completely dominated by Meltdown/Spectre
> > mitigation
> > work. So either 4.11 will be a security focused version or we need
> > to
> > extend the development phase.
>
> Personally I could go either way on this. So unless someone wants to
> argue for switching now (or we significantly extend the development
> window), let's plan on leaving this for post-4.11.
>
Yes, I agree.
And if we don't switch now, I think we should say that, unless someone
argues against your reasoning in your other email, and convince us,
we'll switch as soon as 4.12 is branched (or perhaps as soon as 4.11 is
released?).
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-02-06 22:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 11:36 [PATCH 1/3] Make credit2 the default scheduler George Dunlap
2018-02-05 11:36 ` [PATCH 2/3] xen: Fix credit1 Kconfig entry George Dunlap
2018-02-05 13:35 ` Jan Beulich
2018-02-05 14:43 ` Dario Faggioli
2018-02-05 11:36 ` [PATCH 3/3] xen: Disable ARINC653 scheduler by default for non-DEBUG builds George Dunlap
2018-02-05 13:36 ` Jan Beulich
2018-02-05 14:11 ` George Dunlap
2018-02-05 14:42 ` Dario Faggioli
2018-02-05 14:45 ` George Dunlap
2018-02-05 11:45 ` [PATCH 1/3] Make credit2 the default scheduler Andrew Cooper
2018-02-05 13:01 ` George Dunlap
2018-02-05 16:53 ` Dario Faggioli
2018-02-06 6:18 ` Juergen Gross
2018-02-06 17:02 ` George Dunlap
2018-02-06 22:39 ` Dario Faggioli [this message]
2018-02-07 9:31 ` George Dunlap
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=1517956794.4823.27.camel@suse.com \
--to=dfaggioli@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.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 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).