From: Marcel Apfelbaum <marcel.a@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, pbonzini@redhat.com,
aliguori@us.ibm.com, jan.kiszka@siemens.com, mst@redhat.com
Subject: [Qemu-devel] [PATCH RFC v3 0/2] pci: complete master abort protocol
Date: Mon, 9 Sep 2013 14:21:34 +0300 [thread overview]
Message-ID: <1378725696-13590-1-git-send-email-marcel.a@redhat.com> (raw)
Note: The series is incomplete, for review only
PCI spec requires that a transaction that has not been claimed
by any PCI bus devices will be terminated by the initiator
with "master abort". For read transactions -1(FFFFFFFF) is returned and
writes are silently dropped.
The series deals also with the other aspect of the master abort scenario:
Upon completion the master has to raise RECEIVED MASTER ABORT BIT in
initiator's STATUS register.
Implementation:
- Allowed the MemoryRegion priority to be negative so a subregion will be
visible on all the addresses not covered by the parent MemoryRegion
or other subregions.
- Added a memory region with negative priority that extends over all the
pci address space. This region catches all the accesses
to the unassigned pci addresses.
- The MemoryRegion's ops emulates the master abort scenario.
Note:
For the moment the code assumes that all the reads/writes to
pci address space are done by the cpu.
Changes from v2:
- minor: changed nr of patches int the title
- minor: modified series list
Changes from v1:
- "pci-unassigned-mem" MemoryRegion resides now in PCIBus and not on
various Host Bridges
- "pci-unassgined-mem" does not have a ".valid.accept" field and
implements read write methods
Marcel Apfelbaum (2):
memory: allow MemoryRegion's priority field to accept negative values
hw/pci: handle unassigned pci addresses
hw/pci/pci.c | 46 ++++++++++++++++++++++++++++++++++++++++++++++
include/exec/memory.h | 6 +++---
include/hw/pci/pci_bus.h | 1 +
memory.c | 2 +-
4 files changed, 51 insertions(+), 4 deletions(-)
--
1.8.3.1
next reply other threads:[~2013-09-09 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 11:21 Marcel Apfelbaum [this message]
2013-09-09 11:21 ` [Qemu-devel] [PATCH RFC v3 1/2] memory: allow MemoryRegion's priority field to accept negative values Marcel Apfelbaum
2013-09-09 11:41 ` Michael S. Tsirkin
2013-09-09 11:45 ` Peter Maydell
2013-09-09 11:48 ` Michael S. Tsirkin
2013-09-09 11:49 ` Michael S. Tsirkin
2013-09-09 11:21 ` [Qemu-devel] [PATCH RFC v3 2/2] hw/pci: handle unassigned pci addresses Marcel Apfelbaum
2013-09-14 21:08 ` Michael S. Tsirkin
2013-09-15 6:35 ` Marcel Apfelbaum
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=1378725696-13590-1-git-send-email-marcel.a@redhat.com \
--to=marcel.a@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).