xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Lars Kurth <lars.kurth.xen@gmail.com>
Cc: Juergen Gross <jgross@suse.com>, Wei Liu <wei.liu2@citrix.com>,
	Wen Congyang <wency@cn.fujitsu.com>,
	He Chen <he.chen@linux.intel.com>,
	Doug Goldstein <cardoe@cardoe.com>, Chunyan Liu <cyliu@suse.com>,
	George Dunlap <george.dunlap@citrix.com>,
	ross.lagerwall@citrix.com, Julien Grall <julien.grall@arm.com>,
	mengxu@cis.upenn.edu, Chong Li <lichong659@gmail.com>,
	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: Mon, 9 May 2016 13:37:08 -0400	[thread overview]
Message-ID: <20160509173708.GE16198@char.us.oracle.com> (raw)
In-Reply-To: <6DB04875-03D4-4542-B06C-2B0412D085BE@gmail.com>

On Mon, May 09, 2016 at 04:28:52PM +0100, Lars Kurth wrote:
> Hi all,
> 
> I added the following sections based on git logs to man pages. Authors are on the CC list and should review and modify (or suggest edits by replying to this thread). I added/updated/added TODO's to:
> 
> I do have some questions, to ...
> - Konrad/Ross: is there any documentation for xSplice which I have missed?

I've updated http://wiki.xen.org/wiki/XSplice

to have better layout and data. I will have a sub-section on how to test it.

> - Julien: Any ARM specific stuff you want people to test?
> - Doug: are there any docs / tests for KCONFIG you want to push
> - 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?
> 
> For the following sections there are some TODO's - please verify and modify and once OK, remove the TODO from the wiki pages.
> 
> VCPU-PIN (Juergen Gross)
> - http://wiki.xenproject.org/wiki/Xen_4.7_RC_test_instructions#-f_option_for_xl_vcpu-pin
> 
> RTDS (Meng Xu, Chong Li)
> - Meng, you mention improvements to the RTDS scheduler in another thread
> - Are any specific test instructions needed in http://wiki.xenproject.org/wiki/Xen_4.7_RC_test_instructions
> - http://wiki.xenproject.org/wiki/Xen_4.7_RC_test_instructions#RTDS_scheduler_improvements
> 
> COLO (Wen Congyang)
> - http://wiki.xenproject.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping
> - http://wiki.xenproject.org/wiki/Xen_4.7_RC_test_instructions#COLO_-_Coarse_Grain_Lock_Stepping
> 
> USB (Chunyan Liu)
> - http://wiki.xenproject.org/wiki/Xen_4.7_RC_test_instructions#USB_Support_for_xl
> - http://wiki.xenproject.org/wiki/Xen_USB_Passthrough#PVUSB
> - http://wiki.xenproject.org/wiki/Xen_USB_Passthrough#PVUSB_in_xl.2Flibxl
> 
> CDP (He Chen)
> - http://wiki.xenproject.org/wiki/Xen_4.7_RC_test_instructions#Intel_Code_and_Data_Prioritization_.28CDP.29
> - http://wiki.xenproject.org/wiki/Intel_Platform_QoS_Technologies#Code_and_Data_Prioritization_.28CDP.29
> 
> Are there any other big items that are missing?
> 
> Regards
> Lars
> 
> > On 5 May 2016, at 18:08, Lars Kurth <lars.kurth.xen@gmail.com> wrote:
> > 
> > Hi everyone,
> > 
> > I updated http://wiki.xenproject.org/wiki/Xen_Project_Test_Days and created http://wiki.xenproject.org/wiki/Xen_4.7_RC_test_instructions (note that we only have one page for all RC's now to avoid unnecessary copy and pasting).
> > 
> > For those who want new features to be tested, please expect to 
> > a) Explain what to test (a very short description of the feature)
> > b) Add some instructions on how to test (e.g. some command line instructions)
> > 
> > You can add a new headline (an example is marked with TODO) to either
> > - http://wiki.xenproject.org/wiki/Xen_4.7_RC_test_instructions#Specific_ARM_Test_Instructions
> > - http://wiki.xenproject.org/wiki/Xen_4.7_RC_test_instructions#Specific_x86_Test_Instructions
> > - OR http://wiki.xenproject.org/wiki/Xen_4.7_RC_test_instructions#RC_specific_things_to_test (under a specific RC heading)
> > 
> > I will start promoting Test Days from early next week (on the blog, but also on the mailing lists). The more specific test instructions for Xen 4.7 related features, the better the coverage will be and the more likely people are to actually test.
> > 
> > Best Regards
> > Lars
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2016-05-09 17:37 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
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 [this message]
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=20160509173708.GE16198@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=cardoe@cardoe.com \
    --cc=cyliu@suse.com \
    --cc=george.dunlap@citrix.com \
    --cc=he.chen@linux.intel.com \
    --cc=jgross@suse.com \
    --cc=julien.grall@arm.com \
    --cc=lars.kurth.xen@gmail.com \
    --cc=lichong659@gmail.com \
    --cc=mengxu@cis.upenn.edu \
    --cc=ross.lagerwall@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=wency@cn.fujitsu.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).