All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Ian.Jackson@citrix.com,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH RFC 2/9] ts-unixbench-prep: prep the environment for running unixbench
Date: Wed, 16 Jul 2014 18:07:06 +0200	[thread overview]
Message-ID: <1405526826.5333.109.camel@Solace> (raw)
In-Reply-To: <1405523380.1087.14.camel@kazak.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 3068 bytes --]

On mer, 2014-07-16 at 16:09 +0100, Ian Campbell wrote:
> > ---
> >  ts-unixbench-prep |   79 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> >  1 file changed, 79 insertions(+)
> >  create mode 100755 ts-unixbench-prep
> > 
> > diff --git a/ts-unixbench-prep b/ts-unixbench-prep
> > new file mode 100755
> > index 0000000..607d1a8
> > --- /dev/null
> > +++ b/ts-unixbench-prep
> > @@ -0,0 +1,79 @@
> > +#!/usr/bin/perl -w
> > +# This is part of "osstest", an automated testing framework for Xen.
> > +# Copyright (C) 2009-2013 Citrix Inc.
> 
> Out of date.
> 
Oops. :-)

> > +tsreadconfig();
> > +
> > +# what we expect as argument list is:
> > +#  host=<somehost> [<someguest>]
> > +our $ho= selecthost($ARGV[0]); shift @ARGV;
> 
> IIRC Ian just made select* consume ARGV, so the shift wouldn't be needed
> any more.
> 
Yeah, I saw it. I'll build on top of that as far as it will hit the
repo.

> > +our $gho= $ho;
> > +if ( (0+@ARGV) == 1) {
> 
> Is the 0+ needed, I thought arrays in scalar context evaluated to their
> length already without forcing it like that.
> 
Ehm, my Perl-fu is still very poor. ISTR trying and having some issues,
but yeah, I'll give it another shoot at doing things properly. Sorry :-)

> > +given ($ext) {
> > +  $extract_cmd= 'xf' when ('.tar');
> > +  $extract_cmd= 'zxf' when ['.tgz', '.gzip'];
> > +  $extract_cmd= 'jxf' when  ['.tbz2', '.bz2'];
> > +  default { die "unrecognised file extension $ext" }
> 
> I think "xaf" will automatically handle different compression algs. I'm
> just not quite sure what it does if the tarball is uncompressed.
> 
Oh, I did not know that, I'll give it a try. About the uncompressed
tarball case, I don't think we should worry much about being too
flexible here. Perhaps what I was trying to do above is already too
much. I mean, we expect the file to have a specific name, and to be in a
specific place already, we can well ask for it to be compressed, and
bail if it is not. What do you think?

> > +}
> > +
> > +# Prepare the target, by installing dependencies, and build the benchmark
> > +target_install_packages_norec($gho, qw(build-essential libx11-dev
> > +                                       libgl1-mesa-dev libxext-dev
> > +                                       x11-apps));
> > +target_cmd_root($gho, <<END, 200);
> > +        set -ex
> > +        rm -rf /root/unixbench/
> 
> Ideally you would use the osstest user. I'm not sure if that is set up
> for guests though, might be host only.
> 
I don't recall that either, and I'll check. There are benchmarks,
though, that wants to run as root... I guess that is not a big deal, at
least for guests, is it? For hosts, I see it could be a bigger issue...

Thanks again and 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: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

  parent reply	other threads:[~2014-07-16 16:07 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 [this message]
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 ` [PATCH RFC 5/9] sg-run-job: new recipe for a unixbench job Dario Faggioli
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=1405526826.5333.109.camel@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.