From: Ting-Wei Lan <lantw44@gmail.com>
To: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Cc: lantw44@gmail.com, Keir Fraser <keir@xen.org>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Jan Beulich <jbeulich@suse.com>, Tim Deegan <tim@xen.org>
Subject: Re: [PATCH] build: use correct qemu path in systemd service file and init script
Date: Fri, 24 Jul 2015 01:38:43 +0800 [thread overview]
Message-ID: <55B126A3.3080907@gmail.com> (raw)
In-Reply-To: <1437491457.8383.57.camel@citrix.com>
Ian Campbell 於 西元2015年07月21日 23:10 寫道:
> On Fri, 2015-07-17 at 00:15 +0800, Ting-Wei Lan wrote:
>
> This all looks pretty good. One comment:
>
>> +if test "x$qemu_xen_path" = "x" || test "x$qemu_xen_path" = "xqemu";
>> then :
>> +
>> + qemu_xen_path_service="$LIBEXEC_BIN/qemu-system-i386"
>
> It's a shame we have to repeat the "qemu-system-i386" here and in
> libxl_dm.c.
>
> I think rather than adding a new qemu_xen_path_service we should just
> make the existing $qemu_xen_path default to the full $LIBEXEC_BIN/qemu
> -system-i386 and have it substituted everywhere much like you've done
> here.
>
> Then libxl_dm.c:qemu_xen_path() can return QEMU_XEN_PATH always.
The help strings says:
Use system supplied qemu PATH or qemu (taken from $PATH) as qemu-xen
device model
When $withval is yes, qemu_xen_path() returns "qemu" instead of a full
path, so it cannot use QEMU_XEN_PATH because we are going to change it
to a full path. Although qemu path in service file and init script is
already broken if $withval is yes because we cannot know the full path
of qemu when configuring, I think we still need to keep qemu_xen_path()
working.
>
> What do you think?
>
> Ian.
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-07-23 17:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 16:15 [PATCH] build: use correct qemu path in systemd service file and init script Ting-Wei Lan
2015-07-16 16:30 ` Andrew Cooper
2015-07-16 16:58 ` Ting-Wei Lan
2015-07-21 15:10 ` Ian Campbell
2015-07-23 17:38 ` Ting-Wei Lan [this message]
2015-07-24 8:57 ` Ian Campbell
2015-07-25 16:19 ` Ting-Wei Lan
2015-07-27 7:59 ` Ian Campbell
2015-07-30 6:51 ` [PATCH v2] " Ting-Wei Lan
2015-07-30 10:24 ` Ian Campbell
2015-07-30 10:30 ` Wei Liu
2015-07-30 15:01 ` Ian Campbell
2015-07-30 18:21 ` Ting-Wei Lan
2015-07-30 11:23 ` Anthony PERARD
2015-07-30 11:35 ` Ian Campbell
2015-07-30 15:44 ` Doug Goldstein
2015-07-31 9:13 ` Wei Liu
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=55B126A3.3080907@gmail.com \
--to=lantw44@gmail.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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 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.