From: Avi Kivity <avi@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: aik@ozlabs.ru, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [RFC PATCH] vfio: VFIO PCI driver for Qemu
Date: Thu, 26 Jul 2012 19:06:54 +0300 [thread overview]
Message-ID: <50116B1E.8030209@redhat.com> (raw)
In-Reply-To: <1343314583.3125.17.camel@ul30vt>
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
next prev parent reply other threads:[~2012-07-26 16:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 17:03 [Qemu-devel] [RFC PATCH] vfio: VFIO PCI driver for Qemu Alex Williamson
2012-07-25 19:30 ` Avi Kivity
2012-07-25 19:53 ` Alex Williamson
2012-07-26 8:35 ` Avi Kivity
2012-07-26 14:56 ` Alex Williamson
2012-07-26 15:59 ` Avi Kivity
2012-07-26 16:33 ` Alex Williamson
2012-07-26 16:40 ` Avi Kivity
2012-07-26 19:11 ` Alex Williamson
2012-07-26 16:06 ` Avi Kivity [this message]
2012-07-26 16:40 ` Alex Williamson
2012-07-26 16:47 ` Avi Kivity
2012-07-26 15:09 ` Alex Williamson
2012-07-26 16:34 ` Avi Kivity
2012-07-26 17:40 ` Alex Williamson
2012-07-29 13:47 ` Avi Kivity
2012-07-30 22:29 ` Alex Williamson
2012-07-31 12:34 ` Avi Kivity
2012-07-31 16:56 ` Alex Williamson
2012-07-27 19:22 ` Blue Swirl
2012-07-27 20:28 ` Alex Williamson
2012-07-28 2:55 ` Alexey Kardashevskiy
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=50116B1E.8030209@redhat.com \
--to=avi@redhat.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).