qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, sw@weilnetz.de,
	stefano.stabellini@eu.citrix.com, peter.maydell@linaro.org
Subject: [Qemu-devel] [PATCH memory v2 0/3]  Memory Region Naming - take 2
Date: Mon, 25 Aug 2014 20:08:38 -0700	[thread overview]
Message-ID: <cover.1409018983.git.peter.crosthwaite@xilinx.com> (raw)

Hi,

Here is an attempt at a proper fix to the memory region naming bugs as
reported by Peter. The Xen compile bug and the memory leak.

Regards,
Peter

Changed since v1:
Constify xen physmap name string (Stefan W review).
Change memory_region_name to caching based approach.



Peter Crosthwaite (3):
  xen-hvm: Constify string
  xen: hvm: Abstract away memory region name ref
  memory: Lazy init name from QOM name as needed

 memory.c  |  5 ++++-
 xen-hvm.c | 11 +++++++----
 2 files changed, 11 insertions(+), 5 deletions(-)

-- 
2.1.0.1.g27b9230

             reply	other threads:[~2014-08-26  3:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26  3:08 Peter Crosthwaite [this message]
2014-08-26  3:09 ` [Qemu-devel] [PATCH memory v2 1/3] xen-hvm: Constify string Peter Crosthwaite
2014-08-26  5:37   ` Stefan Weil
2014-08-26  3:09 ` [Qemu-devel] [PATCH memory v2 2/3] xen: hvm: Abstract away memory region name ref Peter Crosthwaite
2014-08-26  3:10 ` [Qemu-devel] [PATCH memory v2 3/3] memory: Lazy init name from QOM name as needed Peter Crosthwaite
2014-08-26 12:51   ` Paolo Bonzini
2014-08-28 14:06   ` Paolo Bonzini
2014-08-28 14:27     ` Peter Crosthwaite
2014-08-28 14:57       ` Paolo Bonzini
2014-08-28 23:17         ` Peter Crosthwaite
2014-09-03  0:17 ` [Qemu-devel] [PATCH memory v2 0/3] Memory Region Naming - take 2 Stefano Stabellini

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=cover.1409018983.git.peter.crosthwaite@xilinx.com \
    --to=peter.crosthwaite@xilinx.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=sw@weilnetz.de \
    /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).