From: Hollis Blanchard <hollis@penguinppc.org>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [kvm-devel] PIO port width on various archs?
Date: Sun, 25 Feb 2007 22:27:47 -0600 [thread overview]
Message-ID: <1172464067.12245.4.camel@diesel> (raw)
In-Reply-To: <45E14F9D.3050502@qumranet.com>
On Sun, 2007-02-25 at 10:58 +0200, Avi Kivity wrote:
> I'm changing the kvm userspace interface to be more friendly to other
> archs. One issue is the PIO port size. x86 uses 16 bits to hold the
> port size (64K ports). Is that an issue for other archs?
>
> I guess I could change it to __u32, but it's better to know what various
> architectures actually require.
PowerPC doesn't have any such concept; access to ISA PIO is done by
having the bridge translate a particular range of MMIO accesses as PIO.
I'm no expert, but I don't know of any mainstream processor other than
x86 that supports PIO.
-Hollis
next prev parent reply other threads:[~2007-02-26 4:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 8:58 PIO port width on various archs? Avi Kivity
2007-02-26 4:27 ` Hollis Blanchard [this message]
2007-02-26 6:13 ` [kvm-devel] " Avi Kivity
2007-02-26 16:52 ` Brian Johnson
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=1172464067.12245.4.camel@diesel \
--to=hollis@penguinppc.org \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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