From: "Andreas Färber" <afaerber@suse.de>
To: Alexander Graf <agraf@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
xen-devel@lists.xensource.com,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
"qemu-ppc@nongnu.org List" <qemu-ppc@nongnu.org>,
Avi Kivity <avi@redhat.com>, Scott Wood <scottwood@freescale.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 00/14] Remove old_portio users for memory region PIO mapping
Date: Mon, 08 Oct 2012 18:18:01 +0200 [thread overview]
Message-ID: <5072FCB9.80606@suse.de> (raw)
In-Reply-To: <1349699033-6703-1-git-send-email-agraf@suse.de>
Am 08.10.2012 14:23, schrieb Alexander Graf:
> When running on PowerPC, we don't have native PIO support. There are a few hacks
> around to enable PIO access on PowerPC nevertheless.
>
> The most typical one is the isa-mmio device. It takes MMIO requests and converts
> them to PIO requests on the (QEMU internal) PIO bus.
>
> This however is not how real hardware works and it limits us in the ability to
> spawn eventfd's on PIO ports which doesn't work with this approach. Instead,
> let's model it more easily. Let's just map the PIO memory region into MMIO
> space.
>
> For this to work, we need to get rid of all old_portio struct users, as they
> break with this approach. This is what this patch set does.
Looks sensible to me as far as reviewed, but I'm missing a patch 13 that
actually rips out old_portio afterwards. :)
Andreas
> It also converts
> the e500 machines and sPAPR to the new memory region model.
>
>
> Alex
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-10-08 16:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 12:23 [PATCH 00/14] Remove old_portio users for memory region PIO mapping Alexander Graf
2012-10-08 12:23 ` [PATCH 01/14] ac97: convert PIO to new memory api read/write Alexander Graf
2012-10-08 12:23 ` [PATCH 02/14] virtio-pci: " Alexander Graf
2012-10-08 12:23 ` [PATCH 03/14] es1370: " Alexander Graf
2012-10-08 12:23 ` [PATCH 04/14] i8254: " Alexander Graf
2012-10-08 12:23 ` [PATCH 05/14] m48t59: " Alexander Graf
2012-10-08 12:23 ` [PATCH 06/14] mc146818rtc: " Alexander Graf
2012-10-08 12:23 ` [PATCH 07/14] pc port92: " Alexander Graf
2012-10-08 12:23 ` [PATCH 08/14] pckbd: " Alexander Graf
2012-10-08 12:23 ` [PATCH 09/14] rtl8139: " Alexander Graf
2012-10-08 12:23 ` [PATCH 10/14] serial: " Alexander Graf
2012-10-08 12:23 ` [PATCH 11/14] vmport: " Alexander Graf
2012-10-08 12:23 ` [PATCH 12/14] xen_platform: " Alexander Graf
2012-10-08 12:23 ` [PATCH 13/14] PPC: e500: Map PIO space into core memory region Alexander Graf
2012-10-08 20:20 ` Scott Wood
2012-10-08 20:48 ` Alexander Graf
2012-10-08 21:05 ` Scott Wood
2012-10-08 21:08 ` Alexander Graf
2012-10-08 21:30 ` Scott Wood
2012-10-08 12:23 ` [PATCH 14/14] PPC: pseries: Remove hack for PIO window Alexander Graf
2012-10-08 16:18 ` Andreas Färber [this message]
2012-10-08 16:32 ` [PATCH 00/14] Remove old_portio users for memory region PIO mapping 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=5072FCB9.80606@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=scottwood@freescale.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).