xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Juergen Gross <jgross@suse.com>
Cc: samuel.thibault@ens-lyon.org, Wei Liu <wei.liu2@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] stubdom: correct dependency for ioemu linkfarm
Date: Mon, 12 Dec 2016 16:08:25 +0000	[thread overview]
Message-ID: <20161212160825.GA25175@citrix.com> (raw)
In-Reply-To: <f8c4f4d1-faa4-2a89-bb96-81fad5d3438f@suse.com>

On Tue, Nov 08, 2016 at 12:18:05PM +0100, Juergen Gross wrote:
> On 08/11/16 11:41, Wei Liu wrote:
> > On Tue, Nov 08, 2016 at 07:29:01AM +0100, Juergen Gross wrote:
> >> The dependency for setting up the links for ioemu is wrong: it is
> >> depending on tools/qemu-xen-traditional-dir which is being modified by
> >> each "make tools" call. This leads to rebuilds of several stubdom
> >> libraries for each call of "make stubdom" as those depend on the ioemu
> >> linkfarm stamp file.
> >>
> >> Modify the dependency to the qemu Makefile instead which is a better
> >> indicator whether we need to create the qemu directory before setting
> >> up the links.
> >>
> >> Signed-off-by: Juergen Gross <jgross@suse.com>
> >> ---
> >>  stubdom/Makefile | 4 ++--
> >>  1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/stubdom/Makefile b/stubdom/Makefile
> >> index 2921f30..0b33e23 100644
> >> --- a/stubdom/Makefile
> >> +++ b/stubdom/Makefile
> >> @@ -281,10 +281,10 @@ IOEMU_LINKFARM_TARGET := ioemu/linkfarm.stamp
> >>  endif
> >>  
> >>  ifeq ($(QEMU_ROOT),.)
> >> -$(XEN_ROOT)/tools/qemu-xen-traditional-dir:
> >> +$(XEN_ROOT)/tools/qemu-xen-traditional-dir/Makefile:
> >>  	$(MAKE) DESTDIR= -C $(XEN_ROOT)/tools qemu-xen-traditional-dir-find
> >>  
> > 
> > What happens if you modify qemu-trad source file(s) and then rebuild
> > stubdom? Will that work correctly after this patch is applied?
> 
> I think so, yes. Make is using the file modification times of the link
> targets to figure out what to rebuild.
> 

I'm afraid I'm still not convinced this patch is the right approach.

The original approach is slower but it always produce the correct
result. The approach in this patch makes things faster but it is not
always correct.

I think I value correctness over speed.

> The only problem which could occur is that adding a file to qemu would
> lead to a link missing. This could be caught by always creating the
> links.

Maybe this is the right approach?

Wei.

> Question is whether this rare case is to be handled properly or
> not. Especially when taking the status of qemu-trad into account: I
> wouldn't expect new source files to show up very often.
> 

> 
> Juergen

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-12-12 16:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08  6:29 [PATCH] stubdom: correct dependency for ioemu linkfarm Juergen Gross
2016-11-08 10:41 ` Wei Liu
2016-11-08 11:18   ` Juergen Gross
2016-12-12 16:08     ` Wei Liu [this message]
2016-12-05 16:36 ` Juergen Gross

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=20161212160825.GA25175@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=jgross@suse.com \
    --cc=samuel.thibault@ens-lyon.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 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).