From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Martin Bligh <mbligh@google.com>
Cc: Avi Kivity <avi@redhat.com>, Alexey Eremenko <al4321@gmail.com>,
autotest@test.kernel.org, Alexey Eromenko <aeromenk@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [Autotest] [KVM-AUTOTEST PATCH] Adding iperf test
Date: Wed, 01 Jul 2009 17:29:13 -0300 [thread overview]
Message-ID: <1246480161.16310.3.camel@freedom> (raw)
In-Reply-To: <33307c790907011016o262b857arad5c8e00ca96d969@mail.gmail.com>
On Wed, 2009-07-01 at 10:16 -0700, Martin Bligh wrote:
> >>>> LMR: me too, hate putting binaries in source tree, but the alternative
> >>>> option is to provide separate *.tar.bz2 for all the binary utils, and
> >>>> I don't sure which way is better.
> >>>>
> >>>
> >>> Yes, I don't have a clear idea as well. It's currently under
> >>> discussion...
> >>>
> >>
> >> Is KVM x86_64 only?
> >>
> >
> > It's x86-64, i386, ia64, s390, and powerpc 44x/e500 only.
>
> OK, then it's difficult to see using binaries? Can we not
> compile these on the system at use time (see the client/deps
> directory for other stuff we do this for)
Biggest trouble is compiling the test under windows hosts. We are
figuring out a way to work around this problem.
next prev parent reply other threads:[~2009-07-01 20:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 21:29 [KVM-AUTOTEST PATCH] Adding iperf test Lucas Meneghel Rodrigues
2009-06-16 21:40 ` Lucas Meneghel Rodrigues
2009-06-16 23:43 ` Lucas Meneghel Rodrigues
2009-06-25 15:54 ` [KVM-AUTOTEST PATCH] bugfix for changing kvm_log to logging Yolkfull Chow
2009-07-01 3:24 ` Lucas Meneghel Rodrigues
2009-06-30 8:52 ` [KVM-AUTOTEST PATCH] Adding iperf test sudhir kumar
2009-06-30 22:46 ` Lucas Meneghel Rodrigues
2009-07-01 11:43 ` Alexey Eremenko
2009-07-01 15:57 ` Lucas Meneghel Rodrigues
2009-07-01 16:18 ` [Autotest] " Martin Bligh
2009-07-01 17:14 ` Avi Kivity
2009-07-01 17:16 ` Martin Bligh
2009-07-01 20:29 ` Lucas Meneghel Rodrigues [this message]
2009-07-02 8:26 ` Avi Kivity
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=1246480161.16310.3.camel@freedom \
--to=lmr@redhat.com \
--cc=aeromenk@redhat.com \
--cc=al4321@gmail.com \
--cc=autotest@test.kernel.org \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mbligh@google.com \
/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