All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	xscript@gmx.net, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] qemu-ga: Fix linux build with trace backend
Date: Mon, 29 Aug 2011 14:33:45 -0500	[thread overview]
Message-ID: <4E5BE999.9050509@linux.vnet.ibm.com> (raw)
In-Reply-To: <4E5BE678.702@mail.berlios.de>

On 08/29/2011 02:20 PM, Stefan Weil wrote:
> Am 29.08.2011 20:32, schrieb Lluís:
>> Stefan Weil writes:
>>> Builds with configure --enable-trace-backend=simple failed on linux
>>> because qemu-ga then uses simpletrace.c which needs get_clock which
>>> needs use_rt_clock which was unresolved.
>>> Adding qemu-timer-common.o fixes this. It adds a little overhead
>>> (about 150 byte).
>>
>> There are a couple of threads associated to this very same topic:
>>
>> http://lists.gnu.org/archive/html/qemu-devel/2011-08/msg02915.html
>> http://lists.gnu.org/archive/html/qemu-devel/2011-08/msg03302.html
>>
>> Lluis
>
> Thanks for the links. So we now have three patch sets for one problem,
> and it will be fixed by a maintainer commit soon :-)
>

4, actually :) An alternative proposal from Blue was setting 
CONFIG_QEMU_TIMER based on whether or not qemu-timer-common.o was needed 
for a particular dependency, so anyone dependent on, say, trace-obj-y 
could just have:

blah-obj-$(CONFIG_QEMU_TIMER) += qemu-timer-common.o

I CC'd you on the patch.

> I personally prefer Blue Swirl's patch (which avoids the overhead)
> or my own patch (which adds a little overhead but is the simplest
> of all three patches). Sorting lists of object files and removing
> duplicates looks strange in my opinion (and might also be bad when
> related code no longer shares the same memory page).
>

I actually preferred the sorted list approach, I think it mirrors how 
most projects handle duplicate header includes and allows for defining a 
self-sufficient group of objects without needed to worry whether 2 
groups list the same object as a dependency. This allows results in one 
group being underspecified and any subsequent user of that group to be 
aware of what's missing.

> With my patch, qemu-ga and the other tools (qemu-io, qemu-img, ...)
> also use similar object lists.
>
> Kind regards,
> Stefan
>
>
>

      reply	other threads:[~2011-08-29 19:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-29 17:46 [Qemu-devel] [PATCH] qemu-ga: Fix linux build with trace backend Stefan Weil
2011-08-29 18:32 ` Lluís
2011-08-29 19:20   ` Stefan Weil
2011-08-29 19:33     ` Michael Roth [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=4E5BE999.9050509@linux.vnet.ibm.com \
    --to=mdroth@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=weil@mail.berlios.de \
    --cc=xscript@gmx.net \
    /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.