qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Jordan Justen <jljusten@gmail.com>
Cc: quintela@redhat.com, Avi Kivity <avi@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] vmstate, memory: decouple vmstate from memory API
Date: Sun, 08 Jan 2012 08:23:43 +0100	[thread overview]
Message-ID: <4F09447F.4090509@weilnetz.de> (raw)
In-Reply-To: <CAFe8ug9EvDZkTLrCpQDYsi2rTHXEPRGKyCWc+jpHq3o4r2njVQ@mail.gmail.com>

Am 08.01.2012 06:14, schrieb Jordan Justen:
> Avi,
> When using pflash_cfi01, I hit the assert(new_block) added above.  It
> seemed to be caused by the low bits of addr being 0x7.  This seems to
> be come from cpu_register_io_memory in memory_region_init_rom_device.
>
> Would this patch be an appropriate fix for this?
>
> diff --git a/exec.c b/exec.c
> index b1d6602..b3ebc91 100644
> --- a/exec.c
> +++ b/exec.c
> @@ -2777,7 +2777,7 @@ void qemu_ram_set_idstr(ram_addr_t addr, const char *name,
>
>       new_block = NULL;
>       QLIST_FOREACH(block,&ram_list.blocks, next) {
> -        if (block->offset == addr) {
> +        if (block->offset == (addr&  TARGET_PAGE_MASK)) {
>               new_block = block;
>               break;
>           }
>
> -Jordan


Hi,

latest QEMU has a different patch for memory.c which fixes the
same problem.

Regards,
Stefan

      reply	other threads:[~2012-01-08  7:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20 14:05 [Qemu-devel] [PATCH 0/2] Decouple vmstate from memory API Avi Kivity
2011-12-20 14:05 ` [Qemu-devel] [PATCH 1/2] memory: introduce memory_region_name() Avi Kivity
2011-12-20 14:05 ` [Qemu-devel] [PATCH 2/2] vmstate, memory: decouple vmstate from memory API Avi Kivity
2011-12-20 14:09   ` Anthony Liguori
2011-12-20 14:16     ` Avi Kivity
2012-01-08  5:14   ` Jordan Justen
2012-01-08  7:23     ` Stefan Weil [this message]

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=4F09447F.4090509@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=avi@redhat.com \
    --cc=jljusten@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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).