From: Bogdan Purcareata <bogdan.purcareata@freescale.com>
To: qemu-ppc@nongnu.org
Cc: Mihai Caraman <mihai.caraman@freescale.com>,
qemu-devel@nongnu.org,
Bogdan Purcareata <bogdan.purcareata@freescale.com>
Subject: [Qemu-devel] [PATCH 2/2] PPC: openpic_kvm: Filter region callbacks based on memory region offset
Date: Wed, 3 Sep 2014 14:36:15 -0400 [thread overview]
Message-ID: <1409769375-22286-3-git-send-email-bogdan.purcareata@freescale.com> (raw)
In-Reply-To: <1409769375-22286-1-git-send-email-bogdan.purcareata@freescale.com>
This is done due to the fact that the kvm-openpic region_{add,del} callbacks
can be invoked for sections generated from other memory regions as well. These
callbacks should handle only requests for the kvm-openpic memory region.
The patch fixes a bug on target-ppc occuring when the "e500-pci-bar0" memory
region is added. This memory region registers an alias to the "e500-ccsr" memory
region, which further contains the "kvm-openpic" subregion. Due to this alias,
the kvm_openpic_region_add is called once more, with an offset within the
"e500-pci-bar" memory region. This generates the remapping of the
in-kernel MPIC at a wrong offset.
The fix consists in an additional filter in kvm_openpic_region_{add,del} to
consider only addresses matching the start of the kvm-openpic memory region.
Signed-off-by: Bogdan Purcareata <bogdan.purcareata@freescale.com>
Signed-off-by: Mihai Caraman <mihai.caraman@freescale.com>
---
hw/intc/openpic_kvm.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/hw/intc/openpic_kvm.c b/hw/intc/openpic_kvm.c
index e3bce04..45d8736 100644
--- a/hw/intc/openpic_kvm.c
+++ b/hw/intc/openpic_kvm.c
@@ -124,7 +124,9 @@ static void kvm_openpic_region_add(MemoryListener *listener,
}
/* Ignore events on regions that are not us */
- if (section->mr != &opp->mem) {
+ if (section->mr != &opp->mem ||
+ section->offset_within_address_space !=
+ memory_region_address_space_offset(section->mr)) {
return;
}
@@ -151,7 +153,9 @@ static void kvm_openpic_region_del(MemoryListener *listener,
int ret;
/* Ignore events on regions that are not us */
- if (section->mr != &opp->mem) {
+ if (section->mr != &opp->mem ||
+ section->offset_within_address_space !=
+ memory_region_address_space_offset(section->mr)) {
return;
}
--
1.7.10.4
next prev parent reply other threads:[~2014-09-03 11:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 18:36 [Qemu-devel] [PATCH 0/2] PPC: kvm: Fix incorrect remapping of in-kernel MPIC Bogdan Purcareata
2014-09-03 18:36 ` [Qemu-devel] [PATCH 1/2] memory: Add MemoryRegion get address space offset helper function Bogdan Purcareata
2014-09-05 15:31 ` [Qemu-devel] [Qemu-ppc] " Scott Wood
2014-09-03 18:36 ` Bogdan Purcareata [this message]
2014-09-05 15:47 ` [Qemu-devel] [Qemu-ppc] [PATCH 2/2] PPC: openpic_kvm: Filter region callbacks based on memory region offset Scott Wood
2014-09-10 11:40 ` bogdan.purcareata
2014-09-10 13:56 ` Alexander Graf
2014-09-11 10:14 ` bogdan.purcareata
2014-09-11 10:27 ` Alexander Graf
2014-09-05 9:07 ` [Qemu-devel] [Qemu-ppc] [PATCH 0/2] PPC: kvm: Fix incorrect remapping of in-kernel MPIC Alexander Graf
2014-09-05 9:08 ` Alexander Graf
2014-09-05 12:59 ` mihai.caraman
2014-09-05 14:31 ` mihai.caraman
2014-09-10 12:49 ` Alexander Graf
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=1409769375-22286-3-git-send-email-bogdan.purcareata@freescale.com \
--to=bogdan.purcareata@freescale.com \
--cc=mihai.caraman@freescale.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).