linux-kernel - Re: [kvm-devel] PIO port width on various archs?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 26 Feb 2007 08:13:40 +0200
From:	Avi Kivity <avi@...ranet.com>
To:	Hollis Blanchard <hollis@...guinppc.org>
CC:	kvm-devel <kvm-devel@...ts.sourceforge.net>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [kvm-devel] PIO port width on various archs?

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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/