From: Dario Faggioli <dario.faggioli@citrix.com>
To: xen-devel@lists.xen.org
Cc: Ian.Jackson@citrix.com, Wei Liu <wei.liu2@citrix.com>,
Ian.Campbell@citrix.com,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: [PATCH RFC 5/9] sg-run-job: new recipe for a unixbench job
Date: Thu, 26 Jun 2014 15:02:55 +0200 [thread overview]
Message-ID: <20140626130255.20110.93479.stgit@Solace> (raw)
In-Reply-To: <20140626124540.20110.24159.stgit@Solace>
Installs and run unixbench inside a PV and an HVM guest.
XXX - The HVM case needs that a few fixup are performed
after ts-debian-hvm-install. I'll do that as a
separate and independent patch.
- This is mostly a proof of concept. I think the
recipes it defines are actually useful, but of
course we can discuss of what is the best course
of actions, depending how we want to achieve.
Signed-off-by: Dario Faggioli <dario.faggioli@citrix.com>
---
sg-run-job | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/sg-run-job b/sg-run-job
index e903869..36b6870 100755
--- a/sg-run-job
+++ b/sg-run-job
@@ -317,6 +317,34 @@ proc run-job/test-rumpuserxen {} {
run-ts . = ts-guest-destroy + host $g
}
+#-------- benchmarks --------
+
+proc bench-unixbench-guest {g} {
+ run-ts . = ts-unixbench-prep + host $g
+ run-ts . = ts-unixbench-run + host $g
+ run-ts . = ts-unixbench-reslts + host $g
+ run-ts . = ts-guest-stop + host $g
+}
+
+proc bench-unixbench-pv {} {
+ run-ts . = ts-debian-install + host
+ run-ts . = ts-debian-fixup + host debian
+ run-ts . = ts-guest-start + host debian
+ bench-unixbench-guest debian
+}
+
+proc bench-unixbench-hvm {} {
+ run-ts . = ts-debian-hvm-install
+ bench-unixbench-guest debianhvm
+}
+
+proc need-hosts/bench-unixbench {} { return host }
+proc run-job/bench-unixbench {} {
+ bench-unixbench-pv
+ #bench-unixbench-hvm TODO: a few fixup needed, will submit as
+ # separate patches.
+}
+
#---------- builds ----------
proc need-hosts/build {} { return BUILD }
next prev parent reply other threads:[~2014-06-26 13:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 13:02 [PATCH RFC 0/9] Running benchmarks via OSSTest Dario Faggioli
2014-06-26 13:02 ` [PATCH RFC 1/9] mg-unixbench-download: new script for downloading the unixbench archive Dario Faggioli
2014-07-16 15:02 ` Ian Campbell
2014-07-16 16:08 ` Dario Faggioli
2014-06-26 13:02 ` [PATCH RFC 2/9] ts-unixbench-prep: prep the environment for running unixbench Dario Faggioli
2014-07-16 15:09 ` Ian Campbell
2014-07-16 15:11 ` Ian Jackson
2014-07-16 15:57 ` Dario Faggioli
2014-07-16 16:07 ` Dario Faggioli
2014-06-26 13:02 ` [PATCH RFC 3/9] ts-unixbench-run: kick off the benchmark on the target Dario Faggioli
2014-06-26 13:02 ` [PATCH RFC 4/9] ts-unixbench-reslts: for retrieving the results Dario Faggioli
2014-07-16 15:11 ` Ian Campbell
2014-07-16 15:58 ` Dario Faggioli
2014-06-26 13:02 ` Dario Faggioli [this message]
2014-06-26 13:03 ` [PATCH RFC 6/9] make-bench-flight: to create a benchmarking flight Dario Faggioli
2014-06-26 13:03 ` [PATCH RFC 7/9] make-flight: introduce a new -t option Dario Faggioli
2014-07-16 15:13 ` Ian Campbell
2014-07-16 15:14 ` Dario Faggioli
2014-06-26 13:03 ` [PATCH RFC 8/9] mg-unixbench-download: make it generic Dario Faggioli
2014-06-26 13:03 ` [PATCH RFC 9/9] ts-unixbench-prep: " Dario Faggioli
2014-06-27 9:40 ` 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=20140626130255.20110.93479.stgit@Solace \
--to=dario.faggioli@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=stefano.stabellini@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.