linux-kernel - Re: [kvm-devel] [PATCH 3/3] virtio PCI device

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]

Message-ID: <474BEDAB.3000305@de.ibm.com>
Date:	Tue, 27 Nov 2007 11:12:59 +0100
From:	Carsten Otte <cotte@...ibm.com>
To:	Avi Kivity <avi@...ranet.com>
CC:	carsteno@...ibm.com,
	Eric Van Hensbergen <ericvanhensbergen@...ibm.com>,
	kvm-devel@...ts.sourceforge.net, lguest <lguest@...abs.org>,
	linux-kernel@...r.kernel.org, virtualization@...ts.osdl.org
Subject: Re: [kvm-devel] [PATCH 3/3] virtio PCI device

Avi Kivity wrote:
> Unfortunately, we have to care for platform differences, subarch 
> differences (vmx/svm), hypervisor differences (with virtio), and guest 
> differences (Linux/Windows/pvLinux, 32/64).  Much care is needed when 
> designing the ABI here.
Yea, I agree.

> [actually thinking a bit, this is specific to the virtio pci binding; 
> s390 will never see any of it]
You remember that we've lost the big debate around virtio in Tucson? 
We intend to bind our virtio devices to PCI too, so that they look the 
same in Linux userland across architectures.
-
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/