All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: yjhyun.yoo@samsung.com, Ian.Jackson@eu.citrix.com,
	Ian Campbell <Ian.Campbell@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: Xen 4.5 development update (July update)
Date: Wed, 23 Jul 2014 15:55:43 +0200	[thread overview]
Message-ID: <53CFBEDF.3090506@m2r.biz> (raw)
In-Reply-To: <alpine.DEB.2.02.1407231444050.2293@kaball.uk.xensource.com>

Il 23/07/2014 15:45, Stefano Stabellini ha scritto:
> On Wed, 23 Jul 2014, Fabio Fantoni wrote:
>> Il 23/07/2014 12:20, Stefano Stabellini ha scritto:
>>> On Wed, 23 Jul 2014, Ian Campbell wrote:
>>>> (trimming CC to just those related to things I've commented on)
>>>>
>>>> On Tue, 2014-07-22 at 20:28 -0400, konrad.wilk@oracle.com wrote:
>>>>
>>>>> fair - still working on it, patches are prototypes or RFC
>>>> You've used this (correctly per your definition here) on various things
>>>> which it seems to me are very unlikely to make it for 4.5, i.e. things
>>>> which are really early prototypes etc, which made me pause every time I
>>>> ready it and have to think back to the definition.
>>>>
>>>> I guess what I'm saying is that "fair" is not a good label for this
>>>> state, it implies that while the thing is a WIP it is still likely to
>>>> make it for 4.5.
>>>>
>>>> I think you need a lower ranked WIP label for things which are in that
>>>> state of prototype/RFC but not likely to make 4.5. "wip" or "inprogress"
>>>> perhaps.
>>>>
>>>>> = Open =
>>>>>
>>>>> == ARM ==
>>>> [...]
>>>>
>>>>> *  ARM VM save/restore/live migration (ok)
>>>>>     -  Junghyun Yoo
>>>> I've not heard from Junghyun since the initial reposting, not sure what
>>>> the prognosis is but given lack of support for SMP and some of the other
>>>> issues I'm more incline to suggest fair rather than OK. Jinghyun, do you
>>>> have any thoughts?
>>>>
>>>> It's possible that the "save/restore/dead-migration" bit is "ok", it's
>>>> the live migration bits where the issues mostly remain iffy.
>>>>
>>>> Also this is dependent on the migration v2 by Andrew et al.
>>>>
>>>>> *  ARM: Use super pages in p2m (ok)
>>>>>      v5 posted
>>>>>     -  Ian Campbell
>>>> Committed.
>>>>
>>>>> == QEMU ==
>>>>>
>>>>> *  Rebase of QEMU 2.0 and SeaBIOS (fair)
>>>>>     -  Ian Jackson
>>>> What is this? Neither of them sound like Ian J things. Stefano maintains
>>>> Qemu and I take care of SeaBIOS.
>>> Yeah, it should be me for QEMU and it is done.
>>>
>>>
>>>> >From the SeaBIOS side we are currently using the latest upstream.
>>>>
>>>> IIRC Stefano has merged the version of qemu which he intends 4.5 to ship
>>>> with, but he should confirm...
>>> Yes, I have already merged QEMU 2.0.0 and I am not planning to merge
>>> again a new QEMU upstream release before 4.5.
>> qemu 2.1 is near to be released, now is rc3, why not update to 2.1?
> I don't think we would have enough time to test it throughly.
However, the major distributions will update to latest qemu tested or 
notin Xen.
I think it's always best to use the latest stable qemu in xen-unstable, 
at least until will xen reach the freeze.

  reply	other threads:[~2014-07-23 13:55 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23  0:28 Xen 4.5 development update (July update) konrad.wilk
2014-07-23  0:47 ` Boris Ostrovsky
2014-07-23 16:09   ` Konrad Rzeszutek Wilk
2014-07-23  8:32 ` Andrew Cooper
2014-07-23  9:51 ` Ian Campbell
2014-07-23 10:20   ` Stefano Stabellini
2014-07-23 12:54     ` Don Slutz
2014-07-23 13:03       ` Stefano Stabellini
2014-07-23 18:34         ` Don Slutz
2014-07-24 11:21           ` Stefano Stabellini
2014-07-28 13:31             ` [PATCH 0/2] Back port Add new machine opt max-ram-below-4g Don Slutz
2014-07-28 13:31               ` [PATCH 1/2] xen-hvm: Fix xen_hvm_init() to adjust pc memory layout Don Slutz
2014-07-28 13:31               ` [PATCH 2/2] Backport pc & q35: Add new machine opt max-ram-below-4g Don Slutz
2014-07-28 16:12               ` [PATCH 0/2] Back port " Stefano Stabellini
2014-07-23 13:42     ` Xen 4.5 development update (July update) Fabio Fantoni
2014-07-23 13:45       ` Stefano Stabellini
2014-07-23 13:55         ` Fabio Fantoni [this message]
2014-07-23 17:02     ` Konrad Rzeszutek Wilk
2014-07-24 11:23       ` Stefano Stabellini
2014-07-25 17:22         ` Konrad Rzeszutek Wilk
2014-07-23 16:18   ` Konrad Rzeszutek Wilk
2014-07-23 16:43     ` Ian Campbell
2014-07-28 17:35 ` Dario Faggioli
2014-08-04 15:44   ` Konrad Rzeszutek Wilk
     [not found] ` <1406569210.4038.28.camel@Solace>
     [not found]   ` <CAENZ-+=pABtLnOU1CE8nHYd48S0_pB4cggLz1zrqQq2V1pcA-w@mail.gmail.com>
2014-07-29  1:37     ` Meng Xu
  -- strict thread matches above, loose matches on Subject: below --
2014-08-15 17:23 konrad.wilk
2014-08-15 17:58 ` Don Slutz
2014-08-15 19:40 ` Jan Beulich
2014-08-15 19:46   ` Konrad Rzeszutek Wilk
2014-08-15 21:19     ` Jan Beulich
2014-08-16  0:31 ` Meng Xu
2014-08-20  9:53   ` Dario Faggioli
2014-08-20 13:40     ` Meng Xu
2014-08-19 16:46 ` Dario Faggioli
2014-08-21 19:17   ` Konrad Rzeszutek Wilk
2014-09-02 20:45 konrad.wilk
2014-09-02 21:25 ` Andrew Cooper
2014-09-03 10:09   ` Ian Campbell
2014-09-03 10:13     ` Wei Liu
2014-09-03 11:27     ` Andrew Cooper
2014-09-03 11:53   ` Shriram Rajagopalan
2014-09-03 11:58     ` Andrew Cooper
2014-09-03 19:54   ` Julien Grall
2014-09-09 14:04     ` Konrad Rzeszutek Wilk
2014-09-03  1:17 ` Hongyang Yang
2014-09-03 12:05   ` Shriram Rajagopalan
2014-09-03  1:23 ` Mukesh Rathor
2014-09-03 12:54 ` Boris Ostrovsky
2014-09-03 15:47 ` Tamas K Lengyel
2014-09-03 15:53 ` Roy Franz
2014-09-09  9:53 ` Ian Campbell
2014-09-09 10:30   ` Jan Beulich
2014-09-09 14:09     ` Konrad Rzeszutek Wilk
2014-09-09 14:30       ` Jan Beulich
2014-09-09 15:48         ` Konrad Rzeszutek Wilk
2014-09-09 14:06   ` Konrad Rzeszutek Wilk
2014-09-09 13:51 ` Meng Xu
2014-09-09 17:02   ` Dario Faggioli

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=53CFBEDF.3090506@m2r.biz \
    --to=fabio.fantoni@m2r.biz \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=yjhyun.yoo@samsung.com \
    /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.