From: Avi Kivity <avi@redhat.com>
To: Martin Bligh <mbligh@google.com>
Cc: Lucas Meneghel Rodrigues <lmr@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 20:14:42 +0300 [thread overview]
Message-ID: <4A4B9982.4090909@redhat.com> (raw)
In-Reply-To: <33307c790907010918n36d78ea5r55c53d1639e6eb3f@mail.gmail.com>
On 07/01/2009 07:18 PM, Martin Bligh wrote:
> On Wed, Jul 1, 2009 at 8:57 AM, Lucas Meneghel Rodrigues<lmr@redhat.com> wrote:
>
>> On Wed, 2009-07-01 at 14:43 +0300, Alexey Eremenko 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.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-07-01 17:13 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 [this message]
2009-07-01 17:16 ` Martin Bligh
2009-07-01 20:29 ` Lucas Meneghel Rodrigues
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=4A4B9982.4090909@redhat.com \
--to=avi@redhat.com \
--cc=aeromenk@redhat.com \
--cc=al4321@gmail.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=lmr@redhat.com \
--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 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.