From: Avi Kivity <avi@redhat.com>
To: Julien Grall <julien.grall@citrix.com>
Cc: qemu-devel@nongnu.org, Stefano.Stabellini@eu.citrix.com
Subject: Re: [Qemu-devel] [PATCH] memory: check address space when a listener is registered
Date: Thu, 05 Apr 2012 13:10:14 +0300 [thread overview]
Message-ID: <4F7D6F86.4090009@redhat.com> (raw)
In-Reply-To: <6645adb9b3662c620ef26b444feec1b02ca06ecc.1333548055.git.julien.grall@citrix.com>
On 04/04/2012 05:15 PM, Julien Grall wrote:
> This patch resolves a bug in memory listener registration.
> "range_add" callback was called on each section of the both
> address space (IO and memory space) even if it doesn't match
> the address space filter.
>
Thanks, applied.
Did you find this bug by inspection, or did it bite you? I thought all
listeners were registered before address spaces were materialized.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-04-05 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 14:15 [Qemu-devel] [PATCH] memory: check address space when a listener is registered Julien Grall
2012-04-05 10:10 ` Avi Kivity [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=4F7D6F86.4090009@redhat.com \
--to=avi@redhat.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=julien.grall@citrix.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).