From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Carlo Marcelo Arenas Belon
<carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [RFC] passthrough for configure options to qemu
Date: Mon, 22 Oct 2007 21:51:24 +0200 [thread overview]
Message-ID: <471CFF3C.10500@qumranet.com> (raw)
In-Reply-To: <20071022185853.GA25818@tapir>
Carlo Marcelo Arenas Belon wrote:
> On Sun, Oct 21, 2007 at 01:25:34PM +0200, Avi Kivity wrote:
>
>> Why not call qemu's ./configure to get the help text?
>>
>
> can be done, I discarded it originally though as it seems pretty hacky as it
> needs the list to be reformatted and filtered further as not all options are
> relevant and some conflict with the ones that the final configure call for qemu
> is going to use, requiring assumptions about qemu which seem to defeat the
> principle of separation that a passthrough provides.
>
> if it wouldn't be that we rely in the --disable-gcc-check description to warn
> users that having kvm crash is expected if not using kvm, I'd say is probably
> better to remove all qemu options from kvm's configure usage() at all
>
>
We can add a note at the end. It doesn't have to be the ultimate in
typography, just usable.
>>> @@ -111,13 +102,10 @@ fi
>>> --disable-kqemu --extra-cflags="-I $PWD/../user $qemu_cflags" \
>>> --extra-ldflags="-L $PWD/../user $qemu_ldflags" \
>>> --enable-kvm --kernel-path="$libkvm_kerneldir" \
>>> - ${enable_alsa:+"--enable-alsa"} \
>>> - ${disable_vnc_tls:+"--disable-vnc-tls"} \
>>> - ${disable_gcc_check:+"--disable-gcc-check"} \
>>> --prefix="$prefix" \
>>> ${qemu_cc:+"--cc=$qemu_cc"} \
>>> ${cross_prefix:+"--cross-prefix=$cross_prefix"} \
>>> - ${cross_prefix:+"--cpu=$arch"}
>>> + ${cross_prefix:+"--cpu=$arch"} $qemu_conf
>>> )
>>>
>> Is it possible in case of a failure due to an unrecognized option to
>> call out usage() instead of qemu's?
>>
>
> not sure what you mean, but qemu's configure ignores any unrecognized options
> so it won't fail.
>
That's a bug. I'm sure qemu-devel would appreciate a patch.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-22 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 15:19 [RFC] passthrough for configure options to qemu Carlo Marcelo Arenas Belon
2007-10-21 11:25 ` Avi Kivity
[not found] ` <471B372E.2080807-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-22 18:58 ` Carlo Marcelo Arenas Belon
2007-10-22 19:51 ` Avi Kivity [this message]
[not found] ` <471CFF3C.10500-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-22 23:49 ` Carlo Marcelo Arenas Belon
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=471CFF3C.10500@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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