From: "Michael S. Tsirkin" <mst@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
Alex Williamson <alex.williamson@redhat.com>,
chrisw@redhat.com, kvm@vger.kernel.org, qemu-devel@nongnu.org,
blauwirbel@gmail.com, ddutile@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 2/2] RAM API: Make use of it for x86 PC
Date: Thu, 18 Nov 2010 18:35:21 +0200 [thread overview]
Message-ID: <20101118163521.GA11896@redhat.com> (raw)
In-Reply-To: <4CE551BE.9020306@redhat.com>
On Thu, Nov 18, 2010 at 06:18:06PM +0200, Avi Kivity wrote:
> >But for PV devices, we can be loose in how we define the way the
> >devices interact with the rest of the system. For instance, we
> >can say that virtio-pci devices are directly connected to RAM and
> >do not go through the memory controllers. That means we could get
> >stable mappings of the virtio ring.
>
> That wouldn't work once we have an iommu and start to assign them to
> nested guests.
Yea. Not sure whether I'm worried about that though.
Mixing in all the problems inherent in nested virt, PV and assigned
devices seems especially masochistic.
> --
> error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-11-18 16:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 16:38 [PATCH 0/2] Minimal RAM API support Alex Williamson
2010-10-29 16:39 ` [PATCH 1/2] " Alex Williamson
2010-10-29 19:57 ` [Qemu-devel] " Blue Swirl
2010-10-29 20:15 ` Alex Williamson
2010-11-01 2:17 ` Isaku Yamahata
2010-11-01 2:32 ` Alex Williamson
2010-10-29 16:39 ` [PATCH 2/2] RAM API: Make use of it for x86 PC Alex Williamson
2010-11-01 15:13 ` [PATCH v2 0/2] Minimal RAM API support Alex Williamson
2010-11-01 15:14 ` [PATCH v2 1/2] " Alex Williamson
2010-11-16 14:55 ` [Qemu-devel] " Anthony Liguori
2010-11-16 15:02 ` Alexander Graf
2010-11-16 15:08 ` Anthony Liguori
2010-11-01 15:14 ` [PATCH v2 2/2] RAM API: Make use of it for x86 PC Alex Williamson
2010-11-16 14:58 ` [Qemu-devel] " Anthony Liguori
2010-11-16 21:24 ` Alex Williamson
2010-11-17 9:31 ` Gleb Natapov
2010-11-17 23:42 ` Anthony Liguori
2010-11-18 15:22 ` Avi Kivity
2010-11-18 15:46 ` Anthony Liguori
2010-11-18 15:57 ` Avi Kivity
2010-11-18 16:09 ` Anthony Liguori
2010-11-18 16:18 ` Avi Kivity
2010-11-18 16:35 ` Michael S. Tsirkin [this message]
2010-11-18 15:51 ` Gleb Natapov
2010-11-18 21:41 ` [PATCH v3 0/2] Minimal RAM API support Alex Williamson
2010-11-18 21:41 ` [PATCH v3 1/2] " Alex Williamson
2010-11-18 21:41 ` [PATCH v3 2/2] RAM API: Make use of it for x86 PC Alex Williamson
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=20101118163521.GA11896@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=chrisw@redhat.com \
--cc=ddutile@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.