From: Avi Kivity <avi@qumranet.com>
To: Hollis Blanchard <hollis@penguinppc.org>
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: Mon, 26 Feb 2007 08:13:40 +0200 [thread overview]
Message-ID: <45E27A94.3020400@qumranet.com> (raw)
In-Reply-To: <1172464067.12245.4.camel@diesel>
Hollis Blanchard wrote:
> 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.
>
>
I think ia64 does, but it's probably exactly the same as x86.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Hollis Blanchard <hollis-yUx37fBWTUITNcAmw9vGhQ@public.gmane.org>
Cc: kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: PIO port width on various archs?
Date: Mon, 26 Feb 2007 08:13:40 +0200 [thread overview]
Message-ID: <45E27A94.3020400@qumranet.com> (raw)
In-Reply-To: <1172464067.12245.4.camel@diesel>
Hollis Blanchard wrote:
> 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.
>
>
I think ia64 does, but it's probably exactly the same as x86.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-02-26 6:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 8:58 PIO port width on various archs? Avi Kivity
2007-02-25 8:58 ` Avi Kivity
2007-02-26 4:27 ` [kvm-devel] " Hollis Blanchard
2007-02-26 4:27 ` Hollis Blanchard
2007-02-26 6:13 ` Avi Kivity [this message]
2007-02-26 6:13 ` Avi Kivity
2007-02-26 16:52 ` Brian Johnson
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=45E27A94.3020400@qumranet.com \
--to=avi@qumranet.com \
--cc=hollis@penguinppc.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.