From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Anthony Liguori <aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Marcelo Tosatti <marcelo-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>,
kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH] KVM: add KVM_SYNC_SHADOW_WITH_USER ioctl (v2)
Date: Sat, 12 Jan 2008 22:57:50 +0200 [thread overview]
Message-ID: <478929CE.9070903@qumranet.com> (raw)
In-Reply-To: <47892303.6030602-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Anthony Liguori wrote:
>>>
>>
>> With mmu notifiers (posted two minutes after this) shadow is
>> implicitly synced with userspace. Since it seems to be progressing
>> rapidly, I won't apply this patch in the hope that mmu notifiers can
>> be ready for 2.6.25.
>
> Does that mean that we'll only support ballooning on host kernels >
> 2.6.25 are you going to do judo with debug registers to implement it
> for older kernels?
Good question. We may choose not to support it (distros may backport it
if they wish), or do some evil hackery, or apply
KVM_SYNC_SHADOW_WITH_USER _only_ to the external module.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
prev parent reply other threads:[~2008-01-12 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 18:17 [PATCH] KVM: add KVM_SYNC_SHADOW_WITH_USER ioctl (v2) Marcelo Tosatti
2008-01-12 19:59 ` Avi Kivity
[not found] ` <47891C10.8060803-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-12 20:28 ` Anthony Liguori
[not found] ` <47892303.6030602-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-01-12 20:57 ` 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=478929CE.9070903@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=marcelo-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.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