From: Avi Kivity <avi@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: "Anthony Liguori" <aliguori@us.ibm.com>,
"Alberto Garcia" <agarcia@igalia.com>,
qemu-devel@nongnu.org, "Paul Brook" <paul@codesourcery.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] Ping [PATCH 0/2] Add TPCI200 and IP-Octal 232 IndustryPack emulation
Date: Sun, 07 Oct 2012 12:13:53 +0200 [thread overview]
Message-ID: <507155E1.6090907@redhat.com> (raw)
In-Reply-To: <CAAu8pHvx+X8QH3mkdwGffKBHyo8teM8wN9wH8Cd4SUUHWt-N1A@mail.gmail.com>
On 10/05/2012 06:24 PM, Blue Swirl wrote:
>
> I'd suppose addressing devices in the bus could be implemented more
> efficiently with better use of memory API, now some of it is
> reimplemented. Maybe Avi can propose something?
Luckily the low-order bits are used for offsets, and the high-order bits
are used for selecting the sub-device.
So you could easily have
struct IPackDevice {
DeviceState qdev;
int32_t slot;
/* IRQ objects for the IndustryPack INT0# and INT1# */
qemu_irq *irq;
MemoryRegion io_space;
MemoryRegion id_space;
MemoryRegion int_space;
MemoryRegion mem8_space; /* for las3 */
MemoryRegion mem16_space; /* for las2 */
};
The PCI device would then just map each space (with
memory_region_add_subregion()) into las1/las2/las3 such that the high
bits select the device/space. The low bits would automatically become
the offset into the space.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-10-07 10:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 13:59 [Qemu-devel] [PATCH 0/2] Add TPCI200 and IP-Octal 232 IndustryPack emulation Alberto Garcia
2012-08-23 13:59 ` [Qemu-devel] [PATCH 1/2] Add TEWS TPCI200 " Alberto Garcia
2012-08-23 13:59 ` [Qemu-devel] [PATCH 2/2] Add IP-Octal 232 " Alberto Garcia
2012-08-31 14:12 ` [Qemu-devel] Ping [PATCH 0/2] Add TPCI200 and " Alberto Garcia
2012-08-31 16:09 ` Andreas Färber
2012-09-10 13:10 ` Alberto Garcia
2012-10-05 13:20 ` Alberto Garcia
2012-10-05 14:28 ` Paolo Bonzini
2012-10-05 14:52 ` Anthony Liguori
2012-10-05 16:24 ` Blue Swirl
2012-10-06 11:29 ` Alberto Garcia
2012-10-07 10:13 ` Avi Kivity [this message]
2012-10-07 10:19 ` Avi Kivity
2012-10-08 8:02 ` Alberto Garcia
2012-10-10 10:24 ` Alberto Garcia
2012-10-10 11:35 ` Avi Kivity
2012-10-10 17:59 ` Alberto Garcia
2012-10-05 14:54 ` Andreas Färber
2012-12-05 13:16 ` [Qemu-devel] [PATCH v2 " Alberto Garcia
2012-12-05 14:03 ` Andreas Färber
2012-12-05 13:16 ` [Qemu-devel] [PATCH v2 1/2] Add TEWS TPCI200 " Alberto Garcia
2012-12-05 13:16 ` [Qemu-devel] [PATCH v2 2/2] Add GE IP-Octal 232 " Alberto Garcia
2012-12-05 15:24 ` [Qemu-devel] [PATCH v3 0/2] Add TPCI200 and " Alberto Garcia
2012-12-17 15:27 ` [Qemu-devel] Ping " Alberto Garcia
2013-01-07 20:32 ` Anthony Liguori
2012-12-05 15:24 ` [Qemu-devel] [PATCH v3 1/2] Add TEWS TPCI200 " Alberto Garcia
2012-12-05 15:24 ` [Qemu-devel] [PATCH v3 2/2] Add GE IP-Octal 232 " Alberto Garcia
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=507155E1.6090907@redhat.com \
--to=avi@redhat.com \
--cc=afaerber@suse.de \
--cc=agarcia@igalia.com \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=paul@codesourcery.com \
--cc=pbonzini@redhat.com \
--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).