All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: valgrind-developers@lists.sourceforge.net
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 0/4] Valgrind updates for Xen 4.3
Date: Wed, 12 Jun 2013 14:45:18 +0100	[thread overview]
Message-ID: <1371044718.24512.438.camel__19486.0223950402$1371044839$gmane$org@zakaz.uk.xensource.com> (raw)
In-Reply-To: <1371044551.24512.436.camel@zakaz.uk.xensource.com>

On Wed, 2013-06-12 at 14:42 +0100, Ian Campbell wrote:
> The following small set of patches updates valgrind for the interface
> changes made in Xen 4.3.
> 
> With this and the two xl patches I just sent to the xen-devel list the
> xl commands list, create (PV guest) and destroy commands are leak free.

I've also attached these to https://bugs.kde.org/show_bug.cgi?id=321065

(I started doing this before I realised I'd have to add the patches
1-by-1 and SPAM the various bugzilla subscribers N times. Sorry about
this -- next time I'll attach them as a tarball...)

Ian.

  parent reply	other threads:[~2013-06-12 13:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1371044551.24512.436.camel@zakaz.uk.xensource.com>
2013-06-12 13:42 ` [PATCH 1/4] xen: distinguish the various fields of the Xen privcmd ioctls in the logging Ian Campbell
2013-06-12 13:42 ` [PATCH 2/4] xen: update for interface changes in Xen 4.3 release Ian Campbell
2013-06-12 13:42 ` [PATCH 3/4] xen: VKI_XEN_SYSCTL_sched_id hypercall Ian Campbell
2013-06-12 13:42 ` [PATCH 4/4] xen: VKI_XENMEM_get_sharing_{freed, shared}_pages hypercall Ian Campbell
2013-06-12 13:45 ` Ian Campbell [this message]
2013-06-12 13:42 [PATCH 0/4] Valgrind updates for Xen 4.3 Ian Campbell

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='1371044718.24512.438.camel__19486.0223950402$1371044839$gmane$org@zakaz.uk.xensource.com' \
    --to=ian.campbell@citrix.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=valgrind-developers@lists.sourceforge.net \
    --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.