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 20:01:53 +0100	[thread overview]
Message-ID: <4EAEF0A1.2010705@weilnetz.de> (raw)
In-Reply-To: <m3bosxko90.fsf@blackfin.pond.sub.org>

Am 31.10.2011 19:30, schrieb Markus Armbruster:
> Copies are evil because we need to pick the one version that's right for
> all our users. Repeatedly.
>
> That's okay (sort of) when there's a tight coupling, and there's really
> only one admissible version.
>
> Or it may be a lesser evil when the thing copied isn't readily available
> (not packaged in common distros).
>
> I can't see either of that for valgrind.h.

Let me add some piece of information for the further discussion.

valgrind.h is an official interface. It is designed to be compatible
across versions.

Initially, I planned to add a valgrind.h copy from my Linux distro.
When I looked at the Valgrind repository, I noticed that the latest
version of valgrind.h had added support for more hosts (ppc, s390)
which I expect will be needed for QEMU soon, so I took this version.

So the decision which copy should be taken is simple: any copy
works as long as it supports your host.

Cheers,
Stefan Weil

  reply	other threads:[~2011-10-31 19:02 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
2011-10-31 18:30       ` Markus Armbruster
2011-10-31 19:01         ` Stefan Weil [this message]
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=4EAEF0A1.2010705@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).