From: Avi Kivity <avi@redhat.com>
To: Muli Ben-Yehuda <muli@il.ibm.com>
Cc: Eran Borovik <BOROVE@il.ibm.com>,
kvm@vger.kernel.org, Ben-Ami Yassour <BENAMI@il.ibm.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [RFC] KVM: Balloon support for device assignment
Date: Sun, 21 Feb 2010 15:25:32 +0200 [thread overview]
Message-ID: <4B81344C.30809@redhat.com> (raw)
In-Reply-To: <20100221131732.GC7677@il.ibm.com>
On 02/21/2010 03:17 PM, Muli Ben-Yehuda wrote:
> On Sun, Feb 21, 2010 at 10:53:25AM +0200, Avi Kivity wrote:
>
>
>> I'm not worried about transition cost (that's for whoever makes the
>> transition to pay) but about how the APIs would translate to the new
>> way of doing things.
>>
>> For example, it might be done using mmu notifiers. We might use the
>> existing madvise(MADV_DONTNEED) as the entry point (though I don't
>> know how we would indicate deflation).
>>
> I guess we could extend mmu notifiers to notify on any PTE transition,
> but that seems like a lot of VM complexity for a little gain, given
> the simple KVM-internal alternatives.
>
mmu notifiers already notify on any pte transition.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-02-21 13:25 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 ` [RFC] KVM: " Avi Kivity
2010-02-17 17:52 ` Muli Ben-Yehuda
2010-02-21 8:53 ` Avi Kivity
[not found] ` <20100221131732.GC7677@il.ibm.com>
2010-02-21 13:25 ` Avi Kivity [this message]
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=4B81344C.30809@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 \
--cc=muli@il.ibm.com \
/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