From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: qemu-devel@nongnu.org
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
borntraeger@de.ibm.com, jfrei@linux.vnet.ibm.com,
Yi Min Zhao <zyimin@cn.ibm.com>,
agraf@suse.de
Subject: [Qemu-devel] [PATCH 4/9] s390x/pci: fix dma notifications in rpcit instruction
Date: Wed, 28 Jan 2015 15:31:33 +0100 [thread overview]
Message-ID: <1422455498-889-5-git-send-email-cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <1422455498-889-1-git-send-email-cornelia.huck@de.ibm.com>
From: Yi Min Zhao <zyimin@cn.ibm.com>
The virtual I/O address range passed to rpcit instruction might not
map to consecutive physical guest pages. For this we have to translate
and create mapping notifications for each vioa page separately.
Signed-off-by: Yi Min Zhao <zyimin@cn.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
---
hw/s390x/s390-pci-inst.c | 20 ++++++++++++--------
1 file changed, 12 insertions(+), 8 deletions(-)
diff --git a/hw/s390x/s390-pci-inst.c b/hw/s390x/s390-pci-inst.c
index c269184..9e5bc5b 100644
--- a/hw/s390x/s390-pci-inst.c
+++ b/hw/s390x/s390-pci-inst.c
@@ -487,7 +487,7 @@ int rpcit_service_call(S390CPU *cpu, uint8_t r1, uint8_t r2)
CPUS390XState *env = &cpu->env;
uint32_t fh;
S390PCIBusDevice *pbdev;
- ram_addr_t size;
+ hwaddr start, end;
IOMMUTLBEntry entry;
MemoryRegion *mr;
@@ -504,7 +504,8 @@ int rpcit_service_call(S390CPU *cpu, uint8_t r1, uint8_t r2)
}
fh = env->regs[r1] >> 32;
- size = env->regs[r2 + 1];
+ start = env->regs[r2];
+ end = start + env->regs[r2 + 1];
pbdev = s390_pci_find_dev_by_fh(fh);
@@ -515,15 +516,18 @@ int rpcit_service_call(S390CPU *cpu, uint8_t r1, uint8_t r2)
}
mr = pci_device_iommu_address_space(pbdev->pdev)->root;
- entry = mr->iommu_ops->translate(mr, env->regs[r2], 0);
+ while (start < end) {
+ entry = mr->iommu_ops->translate(mr, start, 0);
- if (!entry.translated_addr) {
- setcc(cpu, ZPCI_PCI_LS_ERR);
- goto out;
+ if (!entry.translated_addr) {
+ setcc(cpu, ZPCI_PCI_LS_ERR);
+ goto out;
+ }
+
+ memory_region_notify_iommu(mr, entry);
+ start += entry.addr_mask + 1;
}
- entry.addr_mask = size - 1;
- memory_region_notify_iommu(mr, entry);
setcc(cpu, ZPCI_PCI_LS_OK);
out:
return 0;
--
1.7.9.5
next prev parent reply other threads:[~2015-01-28 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 14:31 [Qemu-devel] [PATCH 0/9] s390x bugfixes and cleanup Cornelia Huck
2015-01-28 14:31 ` [Qemu-devel] [PATCH 1/9] s390: Plug memory leak on s390_pci_generate_event() error path Cornelia Huck
2015-01-28 14:31 ` [Qemu-devel] [PATCH 2/9] s390x/pci: avoid sign extension in stpcifc Cornelia Huck
2015-01-28 14:31 ` [Qemu-devel] [PATCH 3/9] s390x/pci: check for invalid function handle Cornelia Huck
2015-01-28 14:31 ` Cornelia Huck [this message]
2015-01-28 14:31 ` [Qemu-devel] [PATCH 5/9] s390x/kvm: Fix diag-308 register decoding Cornelia Huck
2015-01-28 14:31 ` [Qemu-devel] [PATCH 6/9] s390x/kvm: unknown DIAGNOSE code should give a specification exception Cornelia Huck
2015-01-28 14:31 ` [Qemu-devel] [PATCH 7/9] s390x/ipl: Improved code indentation in s390_ipl_init() Cornelia Huck
2015-01-28 14:31 ` [Qemu-devel] [PATCH 8/9] pc-bios/s390-ccw: fix sparse warnings Cornelia Huck
2015-01-28 14:31 ` [Qemu-devel] [PATCH 9/9] pc-bios/s390-ccw: update binary Cornelia Huck
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=1422455498-889-5-git-send-email-cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=zyimin@cn.ibm.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).