qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL] memory core fixes
Date: Mon, 09 Jan 2012 08:51:32 -0600	[thread overview]
Message-ID: <4F0AFEF4.6030201@codemonkey.ws> (raw)
In-Reply-To: <4F09A1A2.7000205@redhat.com>

On 01/08/2012 08:01 AM, Avi Kivity wrote:
> Please pull from
>
>    git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git memory/urgent
>
> to receive fixes for recent memory core breakages.

Pulled.  Thanks.

Regards,

Anthony Liguori

>
> Andreas Färber (2):
>        memory: Fix memory_region_wrong_endianness()
>        memory: Fix adjust_endianness()
>
> Avi Kivity (2):
>        kvm: fix build error in ppc kvm due to
> memory_region_init_ram_ptr() change
>        Fix vmstate_register_ram() for rom/device regions
>
>   memory.c         |    3 ++-
>   savevm.c         |    2 +-
>   target-ppc/kvm.c |    3 ++-
>   3 files changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/memory.c b/memory.c
> index 394cbab..5ab2112 100644
> --- a/memory.c
> +++ b/memory.c
> @@ -843,7 +843,7 @@ static void
> memory_region_destructor_rom_device(MemoryRegion *mr)
>
>   static bool memory_region_wrong_endianness(MemoryRegion *mr)
>   {
> -#ifdef TARGET_BIG_ENDIAN
> +#ifdef TARGET_WORDS_BIGENDIAN
>       return mr->ops->endianness == DEVICE_LITTLE_ENDIAN;
>   #else
>       return mr->ops->endianness == DEVICE_BIG_ENDIAN;
> @@ -942,6 +942,7 @@ static void adjust_endianness(MemoryRegion *mr,
> uint64_t *data, unsigned size)
>               break;
>           case 4:
>               *data = bswap32(*data);
> +            break;
>           default:
>               abort();
>           }
> diff --git a/savevm.c b/savevm.c
> index 88c4bd8..80be1ff 100644
> --- a/savevm.c
> +++ b/savevm.c
> @@ -2284,7 +2284,7 @@ void do_info_snapshots(Monitor *mon)
>
>   void vmstate_register_ram(MemoryRegion *mr, DeviceState *dev)
>   {
> -    qemu_ram_set_idstr(memory_region_get_ram_addr(mr),
> +    qemu_ram_set_idstr(memory_region_get_ram_addr(mr)&  TARGET_PAGE_MASK,
>                          memory_region_name(mr), dev);
>   }
>
> diff --git a/target-ppc/kvm.c b/target-ppc/kvm.c
> index 9b2e605..ce8ac5b 100644
> --- a/target-ppc/kvm.c
> +++ b/target-ppc/kvm.c
> @@ -822,7 +822,8 @@ off_t kvmppc_alloc_rma(const char *name,
> MemoryRegion *sysmem)
>       };
>
>       rma_region = g_new(MemoryRegion, 1);
> -    memory_region_init_ram_ptr(rma_region, NULL, name, size, rma);
> +    memory_region_init_ram_ptr(rma_region, name, size, rma);
> +    vmstate_register_ram_global(rma_region);
>       memory_region_add_subregion(sysmem, 0, rma_region);
>
>       return size;
>

  reply	other threads:[~2012-01-09 14:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-08 14:01 [Qemu-devel] [PULL] memory core fixes Avi Kivity
2012-01-09 14:51 ` Anthony Liguori [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-10-22 10:11 [Qemu-devel] [PULL] Memory " Avi Kivity
2012-10-23 18:08 ` Anthony Liguori

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=4F0AFEF4.6030201@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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).