From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: virtio PCI on KVM without IO BARs Date: Mon, 29 Apr 2013 16:03:22 -0700 Message-ID: <517EFC3A.5050809@zytor.com> References: <20130228152433.GA13832@redhat.com> <517E883C.9010908@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: virtualization@lists.linux-foundation.org, kvm@vger.kernel.org, "Michael S. Tsirkin" To: Don Dutile Return-path: In-Reply-To: <517E883C.9010908@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org List-Id: kvm.vger.kernel.org On 04/29/2013 07:48 AM, Don Dutile wrote: > > c) it's architecture neutral, or can be made architecture neutral. > e.g., inb/outb & PCI ioport support is very different btwn x86 & > non-x86. > A hypercall interface would not have that dependency/difference. > You are joking, right? Hypercalls are if anything *more* architecture and OS dependent. -hpa