From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC PATCH] vfio: VFIO PCI driver for Qemu Date: Thu, 26 Jul 2012 19:06:54 +0300 Message-ID: <50116B1E.8030209@redhat.com> References: <20120725165948.17260.82862.stgit@bling.home> <50104973.3090302@redhat.com> <1343246026.2229.374.camel@bling.home> <50110163.30209@redhat.com> <1343314583.3125.17.camel@ul30vt> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, aik@ozlabs.ru, benh@kernel.crashing.org To: Alex Williamson Return-path: Received: from mx1.redhat.com ([209.132.183.28]:65521 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751180Ab2GZQG7 (ORCPT ); Thu, 26 Jul 2012 12:06:59 -0400 In-Reply-To: <1343314583.3125.17.camel@ul30vt> Sender: kvm-owner@vger.kernel.org List-ID: On 07/26/2012 05:56 PM, Alex Williamson wrote: > > Both KVM and VFIO do strive to make the device in the guest look as much > like it does on bare metal as possible, but we don't guarantee they're > identical and we don't guarantee to match each other. btw, this is somewhat problematic, conceivably this could break a guest (due to a guest bug). But with device assignment the compatibility requirements can be relaxed a bit since there is no live migration. -- error compiling committee.c: too many arguments to function