From: "M. Mohan Kumar" <mohan@in.ibm.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-trivial@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH trivial] configure: explicitly disable virtfs if softmmu=no
Date: Wed, 12 Jun 2013 10:56:57 +0530 [thread overview]
Message-ID: <878v2fucf2.fsf@gmail.com> (raw)
In-Reply-To: <51B76A28.5030008@msgid.tls.msk.ru>
Michael Tokarev <mjt@tls.msk.ru> writes:
> 11.06.2013 21:23, M. Mohan Kumar wrote:
>> Peter Maydell <peter.maydell@linaro.org> writes:
>>
>> How about this approach?
>
> Well, this is definitely wrong :)
>
>> -if test "$softmmu" = yes ; then
>> - if test "$virtfs" != no ; then
>> +
>> +if test "$virtfs" != no ; then
>> + if test "$softmmu" = yes ; then
>> if test "$cap" = yes && test "$linux" = yes && test "$attr" = yes ; then
>> virtfs=yes
>> tools="$tools fsdev/virtfs-proxy-helper\$(EXESUF)"
>> @@ -3415,6 +3416,12 @@ if test "$softmmu" = yes ; then
>> fi
>> virtfs=no
>> fi
>> + else
>> + if test "$virtfs" = yes; then
>> + error_exit "VirtFS is supported only on Linux and requires softmmu"
>> + else
>> + virtfs=no
>> + fi
>> fi
>> if [ "$linux" = "yes" -o "$bsd" = "yes" -o "$solaris" = "yes" ] ; then
>> if [ "$guest_agent" = "yes" ]; then
>
> Now this "if [ $linux..." test is only checked
> if $virtfs != no. Before, it was checked when
> $softmmu != no...
My bad :(, I missed check for guest_agent inside softmmu case.
>
> FWIW, I still don't understand what Peter Maydell dislikes
> in a simplest case I posted initially, where we merely ignore
> (disable) virtfs in case !softmmu. We should probably do the
> same for alot of other features which makes sense only if
> softmmu==yes, and omit many configure tests which are still
> done even if softmmu is disabled, but that's a different
> patch for sure. Maube we should separate out this last linux|bsd|solaris
> test and add another if softmmu there, for readability, so that
> disabling of virtfs will be closer to other virtfs tests.
>
> I applied my initial patch to our debian tree to fix build
> failure for now, because else it fails during build.
>
> Thanks,
>
> /mjt
prev parent reply other threads:[~2013-06-12 5:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 20:47 [Qemu-devel] [PATCH trivial] configure: explicitly disable virtfs if softmmu=no Michael Tokarev
2013-06-10 20:57 ` Michael Tokarev
2013-06-11 9:22 ` M. Mohan Kumar
2013-06-11 9:24 ` Peter Maydell
2013-06-11 9:47 ` Michael Tokarev
2013-06-10 21:45 ` Peter Maydell
2013-06-11 12:29 ` Michael Tokarev
2013-06-11 15:01 ` Peter Maydell
2013-06-11 17:23 ` M. Mohan Kumar
2013-06-11 18:19 ` Michael Tokarev
2013-06-11 19:21 ` Peter Maydell
2013-06-11 19:55 ` Michael Tokarev
2013-06-12 5:26 ` M. Mohan Kumar [this message]
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=878v2fucf2.fsf@gmail.com \
--to=mohan@in.ibm.com \
--cc=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).