From: Juergen Gross <jgross@suse.com>
To: Dario Faggioli <dario.faggioli@citrix.com>, xen-devel@lists.xen.org
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [OSSTEST PATCH 0/2] Test case for cpupools
Date: Thu, 18 Dec 2014 15:56:55 +0100 [thread overview]
Message-ID: <5492EB37.3050004@suse.com> (raw)
In-Reply-To: <20141218130919.29909.13566.stgit@Abyss.station>
On 12/18/2014 02:38 PM, Dario Faggioli wrote:
> Just the fact that we are not doing anything to smoke test cpupools, while I
> think we should. :-)
>
> This add something quite basic, but it's, IMO, already representative one
> typically does with cpupools. We can add more pCPU related tricks (removing,
> adding, etc), or we can add more domains and move them around more, of course.
> If anyone has any suggestion about operations that should really be part of
> Osstest's runs, let me know and I'll include them.
>
> As it is right now, the test is super quick, to the point that I considered
> whether it wouldn't have been better to add some similar cpupool operations in
> one of the existing jobs. I ended up deciding for having a separate job,
> because this is, after all, a rather specific operation, and a different enough
> thing from basic VM lifecycle, so I think it deserves its own job.
>
> Thanks and Regards, Dario
Thanks for doing this!
Juergen
>
> ---
>
> Dario Faggioli (2):
> ts-cpupools: new test script
> Testing cpupools: recipe for it and job definition
>
>
> make-flight | 11 +++++
> sg-run-job | 6 +++
> ts-cpupools | 124 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 141 insertions(+)
> create mode 100755 ts-cpupools
>
> --
> <<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)
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
prev parent reply other threads:[~2014-12-18 14:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 13:38 [OSSTEST PATCH 0/2] Test case for cpupools Dario Faggioli
2014-12-18 13:38 ` [OSSTEST PATCH 1/2] ts-cpupools: new test script Dario Faggioli
2014-12-18 14:57 ` Juergen Gross
2014-12-18 13:39 ` [OSSTEST PATCH 2/2] Testing cpupools: recipe for it and job definition Dario Faggioli
2014-12-18 15:00 ` Juergen Gross
2014-12-18 15:04 ` Wei Liu
2014-12-18 15:10 ` Juergen Gross
2014-12-18 17:29 ` Dario Faggioli
2014-12-19 9:48 ` Ian Campbell
2014-12-19 10:50 ` Dario Faggioli
2014-12-19 11:02 ` Ian Campbell
2014-12-18 13:44 ` [OSSTEST PATCH 0/2] Test case for cpupools Dario Faggioli
2014-12-18 14:56 ` Juergen Gross [this message]
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=5492EB37.3050004@suse.com \
--to=jgross@suse.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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.