From: Kevin Wolf <kwolf@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: look for qemu-iotests-$ARCH
Date: Wed, 08 Jul 2009 10:34:35 +0200 [thread overview]
Message-ID: <4A545A1B.1080606@redhat.com> (raw)
In-Reply-To: <20090707180346.GA6233@lst.de>
Christoph Hellwig schrieb:
> Look for the binary as installed by qemu make install instead of
> requiring the qemu symlink. Note that we need a couple of regular
> expressions to munge the uname output into the architecture name
> qemu expects.
I don't completely understand your goal here. Why would you want to use
the host architecture for the guest, too? If anything this makes tests
behave differently on different hosts. If, say, qemu-system-x86_64 is
available depends on the configure options rather than on the host. And
qemu isn't a symlink AFAIK, but the traditional name of qemu-system-i386
(or has this changed recently?).
Kevin
next prev parent reply other threads:[~2009-07-08 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 18:03 [Qemu-devel] [PATCH] qemu-iotests: look for qemu-iotests-$ARCH Christoph Hellwig
2009-07-08 8:34 ` Kevin Wolf [this message]
2009-07-08 10:59 ` Christoph Hellwig
2009-07-08 11:09 ` Kevin Wolf
2009-07-08 11:21 ` Christoph Hellwig
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=4A545A1B.1080606@redhat.com \
--to=kwolf@redhat.com \
--cc=hch@lst.de \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).