From: Dario Faggioli <dario.faggioli@citrix.com>
To: Lars Kurth <lars.kurth.xen@gmail.com>,
George Dunlap <george.dunlap@citrix.com>,
Juergen Gross <jgross@suse.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen 4.7 Test Day Instructions for RC2+ : Call to action for people who added new features / functionality to Xen 4.7
Date: Tue, 10 May 2016 04:18:08 +0200 [thread overview]
Message-ID: <1462846688.4858.5.camel@citrix.com> (raw)
In-Reply-To: <4AFA19A9-28D2-4506-894C-E5854ADC77DB@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1119 bytes --]
[removing Vitaly, adding Juergen]
On Mon, 2016-05-09 at 17:55 +0100, Lars Kurth wrote:
>
> > On 9 May 2016, at 17:03, George Dunlap <george.dunlap@citrix.com>
> > wrote:
> > On Mon, May 9, 2016 at 4:28 PM, Lars Kurth
> > <lars.kurth.xen@gmail.com> wrote:
> > >
> > > - George: are there any manual tests for credit 2 hard affinity,
> > > for hotplug disk backends (drbd, iscsi, &c) and soft reset for
> > > HVM guests that should be added?
> > Hard affinity tests shouldn't be too difficult to add in.
>
> That would be great
>
George, if you are not into this already, I can do it.
One thing (for Lars). There's a section about "-f option for xl vcpu-
pin". I don't see what's its purpose and what and how one should test
this.
Perhaps Juergen has better ideas, but I think it should just be
removed.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-10 2:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 17:08 Xen 4.7 Test Day Instructions for RC2+ : Call to action for people who added new features / functionality to Xen 4.7 Lars Kurth
2016-05-09 15:28 ` Lars Kurth
2016-05-09 16:03 ` George Dunlap
2016-05-09 16:55 ` Lars Kurth
2016-05-10 2:18 ` Dario Faggioli [this message]
2016-05-10 4:02 ` Juergen Gross
2016-05-10 8:46 ` George Dunlap
2016-05-12 8:04 ` Dario Faggioli
2016-05-09 16:17 ` Julien Grall
2016-05-09 16:56 ` Lars Kurth
2016-05-09 17:11 ` Julien Grall
2016-05-10 10:04 ` Stefano Stabellini
2016-05-10 1:12 ` Shannon Zhao
2016-05-09 17:14 ` Meng Xu
2016-05-09 17:37 ` Konrad Rzeszutek Wilk
2016-05-09 17:39 ` Lars Kurth
2016-05-10 2:53 ` Chun Yan Liu
2016-05-10 2:59 ` Doug Goldstein
2016-05-10 7:50 ` Kconfig docs [was: Re: Xen 4.7 Test Day Instructions for RC2+ : Call to action for people who added new features / functionality to Xen 4.7] Dario Faggioli
2016-05-10 14:31 ` Xen 4.7 Test Day Instructions for RC2+ : Call to action for people who added new features / functionality to Xen 4.7 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=1462846688.4858.5.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jgross@suse.com \
--cc=lars.kurth.xen@gmail.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).