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 fix
Date: Thu, 22 Sep 2011 10:58:31 -0500 [thread overview]
Message-ID: <4E7B5B27.2090706@codemonkey.ws> (raw)
In-Reply-To: <4E79D773.6040406@redhat.com>
On 09/21/2011 07:24 AM, Avi Kivity wrote:
> Please pull from
>
> git://github.com/avikivity/qemu.git memory/core
Pulled. Thanks.
Regards,
Anthony Liguori
> to receive the following fix:
>
> Michael Walle (1):
> memory: fix subregion collision warning
>
> memory.c | 13 ++++++++-----
> 1 files changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/memory.c b/memory.c
> index 101b67c..ba74435 100644
> --- a/memory.c
> +++ b/memory.c
> @@ -1190,16 +1190,19 @@ static void
> memory_region_add_subregion_common(MemoryRegion *mr,
> if (subregion->may_overlap || other->may_overlap) {
> continue;
> }
> - if (offset >= other->offset + other->size
> - || offset + subregion->size <= other->offset) {
> + if (offset >= other->addr + other->size
> + || offset + subregion->size <= other->addr) {
> continue;
> }
> #if 0
> - printf("warning: subregion collision %llx/%llx vs %llx/%llx\n",
> + printf("warning: subregion collision %llx/%llx (%s) "
> + "vs %llx/%llx (%s)\n",
> (unsigned long long)offset,
> (unsigned long long)subregion->size,
> - (unsigned long long)other->offset,
> - (unsigned long long)other->size);
> + subregion->name,
> + (unsigned long long)other->addr,
> + (unsigned long long)other->size,
> + other->name);
> #endif
> }
> QTAILQ_FOREACH(other, &mr->subregions, subregions_link) {
>
prev parent reply other threads:[~2011-09-22 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 12:24 [Qemu-devel] [PULL] memory core fix Avi Kivity
2011-09-22 15:58 ` Anthony Liguori [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=4E7B5B27.2090706@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 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.