From: Pierre Morel <pmorel@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: cohuck@redhat.com, agraf@suse.de, borntraeger@de.ibm.com,
zyimin@linux.vnet.ibm.com, mst@redhat.com, thuth@redhat.com,
pasic@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH v4 5/7] s390x/pci: move the memory region read from pcilg
Date: Thu, 30 Nov 2017 13:55:28 +0100 [thread overview]
Message-ID: <1512046530-17773-6-git-send-email-pmorel@linux.vnet.ibm.com> (raw)
In-Reply-To: <1512046530-17773-1-git-send-email-pmorel@linux.vnet.ibm.com>
Let's move the memory region read from pcilg into a dedicated function.
This allows us to prepare a later patch.
Signed-off-by: Pierre Morel <pmorel@linux.vnet.ibm.com>
Reviewed-by: Yi Min Zhao <zyimin@linux.vnet.ibm.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
---
hw/s390x/s390-pci-inst.c | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/hw/s390x/s390-pci-inst.c b/hw/s390x/s390-pci-inst.c
index bab7353..c702e8d 100644
--- a/hw/s390x/s390-pci-inst.c
+++ b/hw/s390x/s390-pci-inst.c
@@ -345,13 +345,22 @@ static int zpci_endian_swap(uint64_t *ptr, uint8_t len)
return 0;
}
+static MemTxResult zpci_read_bar(S390PCIBusDevice *pbdev, uint8_t pcias,
+ uint64_t offset, uint64_t *data, uint8_t len)
+{
+ MemoryRegion *mr;
+
+ mr = pbdev->pdev->io_regions[pcias].memory;
+ return memory_region_dispatch_read(mr, offset, data, len,
+ MEMTXATTRS_UNSPECIFIED);
+}
+
int pcilg_service_call(S390CPU *cpu, uint8_t r1, uint8_t r2)
{
CPUS390XState *env = &cpu->env;
S390PCIBusDevice *pbdev;
uint64_t offset;
uint64_t data;
- MemoryRegion *mr;
MemTxResult result;
uint8_t len;
uint32_t fh;
@@ -402,9 +411,7 @@ int pcilg_service_call(S390CPU *cpu, uint8_t r1, uint8_t r2)
program_interrupt(env, PGM_OPERAND, 4);
return 0;
}
- mr = pbdev->pdev->io_regions[pcias].memory;
- result = memory_region_dispatch_read(mr, offset, &data, len,
- MEMTXATTRS_UNSPECIFIED);
+ result = zpci_read_bar(pbdev, pcias, offset, &data, len);
if (result != MEMTX_OK) {
program_interrupt(env, PGM_OPERAND, 4);
return 0;
--
2.7.4
next prev parent reply other threads:[~2017-11-30 12:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 12:55 [Qemu-devel] [PATCH v4 0/7] s390x/pci: Improve zPCI to cover more cases Pierre Morel
2017-11-30 12:55 ` [Qemu-devel] [PATCH v4 1/7] s390x/pci: factor out endianess conversion Pierre Morel
2017-11-30 12:55 ` [Qemu-devel] [PATCH v4 2/7] s390x/pci: rework PCI STORE Pierre Morel
2017-12-01 10:37 ` Cornelia Huck
2017-11-30 12:55 ` [Qemu-devel] [PATCH v4 3/7] s390x/pci: rework PCI LOAD Pierre Morel
2017-12-01 10:38 ` Cornelia Huck
2017-11-30 12:55 ` [Qemu-devel] [PATCH v4 4/7] s390x/pci: rework PCI STORE BLOCK Pierre Morel
2017-11-30 12:55 ` Pierre Morel [this message]
2017-11-30 12:55 ` [Qemu-devel] [PATCH v4 6/7] s390x/pci: move the memory region write from pcistg Pierre Morel
2017-11-30 12:55 ` [Qemu-devel] [PATCH v4 7/7] s390x/pci: search for subregion inside the BARs Pierre Morel
2017-12-01 10:29 ` [Qemu-devel] [PATCH v4 0/7] s390x/pci: Improve zPCI to cover more cases Cornelia Huck
2017-12-01 12:58 ` Pierre Morel
2017-12-01 15:39 ` 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=1512046530-17773-6-git-send-email-pmorel@linux.vnet.ibm.com \
--to=pmorel@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=zyimin@linux.vnet.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).