public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: borove@il.ibm.com
Cc: kvm@vger.kernel.org, benami@il.ibm.com,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [RFC] KVM: Balloon support for device assignment
Date: Wed, 17 Feb 2010 12:27:09 +0200	[thread overview]
Message-ID: <4B7BC47D.4030808@redhat.com> (raw)
In-Reply-To: <1266399807-4498-2-git-send-email-borove@il.ibm.com>

On 02/17/2010 11:43 AM, borove@il.ibm.com wrote:
> From: Eran Borovik<borove@il.ibm.com>
>
> This patch adds modifications to allow correct
> balloon operation when a virtual guest uses a direct assigned device.
> The modifications include a new interface between qemu and kvm to allow
> mapping and unmapping the pages from the IOMMU as well as pinning and unpinning as needed.
>    

The plan for iommu support is to push it into uio.  Instead of kvm 
managing the iommu directly, I'd like qemu to open a uio device and set 
up an iommu mapping there, which will just happen to match the kvm 
memory slots.  Similarly, interrupts will be forwarded using irqfds.  
This will allow using the iommu without kvm, and reduce the amount of 
special purpose kvm code.

These patches make the transition more difficult which worries me.  I 
know Gerd looked at making the move, but no longer.

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2010-02-17 10:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17  9:43 [RFC] Balloon support for device assignment borove
2010-02-17  9:43 ` [RFC] KVM: " borove
2010-02-17  9:43   ` [RFC] QEMU: " borove
2010-02-17 10:28     ` Avi Kivity
2010-02-17 10:27   ` Avi Kivity [this message]
2010-02-17 17:52     ` [RFC] KVM: " Muli Ben-Yehuda
2010-02-21  8:53       ` Avi Kivity
     [not found]         ` <20100221131732.GC7677@il.ibm.com>
2010-02-21 13:25           ` Avi Kivity

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=4B7BC47D.4030808@redhat.com \
    --to=avi@redhat.com \
    --cc=benami@il.ibm.com \
    --cc=borove@il.ibm.com \
    --cc=kraxel@redhat.com \
    --cc=kvm@vger.kernel.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