All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: "Wei Liu" <Wei.Liu2@citrix.com>,
	"Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>,
	"Fabio Fantoni" <fabio.fantoni@heliman.it>,
	xen-devel <xen-devel@lists.xenproject.org>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: Xen 4.4 development update: RC0 imminent
Date: Thu, 5 Dec 2013 17:05:28 +0000	[thread overview]
Message-ID: <52A0B258.5090202@eu.citrix.com> (raw)
In-Reply-To: <52A0B103.5000300@citrix.com>

On 12/05/2013 04:59 PM, David Vrabel wrote:
> On 05/12/13 16:29, George Dunlap wrote:
>>   
>> Features which might be worth highlighting for testing in blogs:
>>
>> * Event channel scalability
>>   - David Vrabel
> I have a pending critical bug fix which I am running through some
> automated tests right now.  There's not much point in testing this
> without the fix.
>
> I was also going to schedule some more extensive testing when a slot
> becomes available, but if RC0 is imminent I will post the fix tomorrow
> rather than waiting for further testing.
>
>> * kexec -- is this worth testing?
>>   - David Vrabel
> Everything is worth testing...  This has already seen a fair amount of
> testing by various people already (as well as extensive testing in
> XenServer's automated test system) so I don't think it needs to be
> called out specifically for more testing.

OK -- but is it something that is worthwhile calling out specifically as 
a cool new feature?  Is it the kind of thing for which it would be 
helpful to raise awareness?

  -George

  reply	other threads:[~2013-12-05 17:05 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 16:09 Xen 4.4 development update: RC0 imminent George Dunlap
2013-12-05 16:29 ` George Dunlap
2013-12-05 16:34   ` Wei Liu
2013-12-05 16:39     ` George Dunlap
2013-12-05 16:48       ` Wei Liu
2013-12-05 16:59         ` Ian Campbell
2013-12-05 17:06           ` Wei Liu
2013-12-05 17:16             ` Ian Campbell
2013-12-05 17:34               ` Wei Liu
2013-12-05 17:53                 ` George Dunlap
2013-12-05 18:03                   ` Wei Liu
2013-12-06  9:27                     ` Ian Campbell
2013-12-06 10:51                       ` Wei Liu
2013-12-05 16:39   ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-05 16:41     ` George Dunlap
2013-12-05 16:42   ` Roger Pau Monné
2013-12-05 16:51     ` George Dunlap
2013-12-05 17:01       ` Lars Kurth
2013-12-05 17:04         ` George Dunlap
2013-12-05 20:06           ` Russell Pavlicek
2013-12-05 23:54             ` Sander Eikelenboom
2013-12-06  9:39             ` Lars Kurth
2013-12-06 12:14             ` George Dunlap
2013-12-05 16:59   ` David Vrabel
2013-12-05 17:05     ` George Dunlap [this message]
2013-12-05 17:40       ` Dario Faggioli
2013-12-05 17:07     ` George Dunlap
2013-12-05 17:01   ` Olaf Hering
2013-12-05 17:06     ` David Vrabel
2013-12-05 17:32   ` Dario Faggioli
2013-12-06 13:30   ` Fabio Fantoni
2013-12-05 16:34 ` Andrew Cooper
2013-12-06  9:07   ` Jan Beulich
2013-12-06 13:07     ` George Dunlap
2013-12-06 14:58       ` Jan Beulich
2013-12-05 16:54 ` George Dunlap
2013-12-16 10:50   ` Lars Kurth

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=52A0B258.5090202@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Wei.Liu2@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=fabio.fantoni@heliman.it \
    --cc=phcoder@gmail.com \
    --cc=roger.pau@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.