From: Avi Kivity <avi@redhat.com>
To: Michael Walle <michael@walle.cc>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] new memory api: offsets?
Date: Thu, 01 Sep 2011 08:54:28 +0300 [thread overview]
Message-ID: <4E5F1E14.3060606@redhat.com> (raw)
In-Reply-To: <201109010054.53424.michael@walle.cc>
On 09/01/2011 01:54 AM, Michael Walle wrote:
> Hi Avi,
>
> while debugging, i noticed, that mr->offset is never set, expect in the
> initializer. (The subregion collision warning is printed although the regions
> are not overlapping.) Is this intended?
Did you miss memory_region_set_offset()?
The subregion collision warning is unrelated?
> btw. you may include the memory region name in the warning.
>
sure, patches welcome.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2011-09-01 5:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 22:54 [Qemu-devel] new memory api: offsets? Michael Walle
2011-09-01 5:54 ` Avi Kivity [this message]
2011-09-01 10:00 ` Michael Walle
2011-09-06 7:50 ` Avi Kivity
2011-09-15 21:16 ` [Qemu-devel] [PATCH] memory: fix subregion collision warning Michael Walle
2011-09-18 11:55 ` Avi Kivity
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=4E5F1E14.3060606@redhat.com \
--to=avi@redhat.com \
--cc=michael@walle.cc \
--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).