qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Markus Armbruster <armbru@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, Alexander Graf <agraf@suse.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Support running QEMU on Valgrind
Date: Mon, 31 Oct 2011 18:09:01 +0100	[thread overview]
Message-ID: <4EAED62D.3080602@weilnetz.de> (raw)
In-Reply-To: <m3ipn5mzs0.fsf@blackfin.pond.sub.org>

Am 31.10.2011 07:38, schrieb Markus Armbruster:
> Alexander Graf <agraf@suse.de> writes:
>> On 30.10.2011, at 13:07, Stefan Weil wrote:
>>> Valgrind is a tool which can automatically detect many kinds of bugs.
>>>
>>> Running QEMU on Valgrind with x86_64 hosts was not possible because
>>> Valgrind aborts when memalign is called with an alignment larger than
>>> 1 MiB. QEMU normally uses 2 MiB on Linux x86_64.
>>>
>>> Now the alignment is reduced to the page size when QEMU is running on
>>> Valgrind.
>>>
>>> valgrind.h is a copy from Valgrind svn trunk r12226 with trailing
>>> whitespace stripped but otherwise unmodified, so it still raises lots
>>> of errors when checked with scripts/checkpatch.pl.
>>
>> Can't we just require valgrind header files to be around when kvm is 
>> enabled? I would rather not copy code from other projects. 
>> Alternatively you could take the header and shrink it down to maybe 5 
>> lines of inline asm code that would be a lot more readable :). You're 
>> #ifdef'ing on x86_64 already anyways.
>>
>>>
>>> It is included here to avoid a dependency on Valgrind.
> Our usual way to avoid a hard dependency on something we want is to
> detect it in configure, then do something like
>
> #ifdef CONFIG_VALGRIND
> #include "valgrind.h"
> #else
> #define RUNNING_ON_VALGRIND 0
> #endif
>
> [...]

Markus, you obviously did not read my last mail.
I know how configure works, so there is no need to teach me.

I wrote that I decided against the configure solution because
it is not adequate here. Adding a copy of valgrind.h which
is explicitly made for being copied is simpler and better:

* It avoids code in configure. There are already so many
   checks in configure that it takes a rather long time to run,
   and additional checks don't improve maintainability.

* It adds Valgrind support for any x86_64 QEMU binary
   without enforcing a build dependency on Valgrind.
   This is useful for QEMU packages in distributions.

You said that copies are evil without explaining why you
think so. What about the other copies in QEMU? There are
lots of them, and some (e.g. the Linux headers) were added
recently.

Cheers,
Stefan Weil

  reply	other threads:[~2011-10-31 17:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-30 12:07 [Qemu-devel] [PATCH] Support running QEMU on Valgrind Stefan Weil
2011-10-30 13:41 ` Alexander Graf
2011-10-30 14:30   ` Stefan Weil
2011-10-30 14:45     ` Alexander Graf
2011-10-31  6:44       ` Markus Armbruster
2011-10-31  6:38   ` Markus Armbruster
2011-10-31 17:09     ` Stefan Weil [this message]
2011-10-31 18:30       ` Markus Armbruster
2011-10-31 19:01         ` Stefan Weil
2011-10-31 18:13 ` Anthony Liguori
2011-10-31 19:03   ` Stefan Weil
2011-10-31 19:19     ` Anthony Liguori
2011-10-31 18:22 ` Daniel P. Berrange
2011-10-31 18:51   ` Stefan Weil

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=4EAED62D.3080602@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=agraf@suse.de \
    --cc=armbru@redhat.com \
    --cc=avi@redhat.com \
    --cc=qemu-devel@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).