From: Avi Kivity <avi@qumranet.com>
To: Christoph Hellwig <hch@infradead.org>,
Avi Kivity <avi@qumranet.com>, Shaohua Li <shaohua.li@intel.com>,
kvm-devel <kvm-devel@lists.sourceforge.net>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [kvm-devel] [RFC 0/8]KVM: swap out guest pages
Date: Mon, 23 Jul 2007 15:29:36 +0300 [thread overview]
Message-ID: <46A49F30.5010206@qumranet.com> (raw)
In-Reply-To: <20070723122510.GA3674@infradead.org>
Christoph Hellwig wrote:
> On Mon, Jul 23, 2007 at 01:27:40PM +0300, Avi Kivity wrote:
>
>> Having an address_space (like your patch does) is remarkably simple, and
>> requires few hooks from the current vm. However using existing vmas
>> mapped by the user has many advantages:
>>
>
> Actually it requires lots of deep down VM internals symbols that'll never
> get exported.
>
>
What's "it" here? kvm-specific address space or generic vmas.
Generic vmas will be more intrusive AFAICT.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2007-07-23 12:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 6:51 [RFC 0/8]KVM: swap out guest pages Shaohua Li
2007-07-23 10:27 ` Avi Kivity
2007-07-23 12:25 ` [kvm-devel] " Christoph Hellwig
2007-07-23 12:29 ` Avi Kivity [this message]
2007-07-23 12:34 ` Christoph Hellwig
2007-07-23 12:39 ` Avi Kivity
2007-07-24 2:00 ` Shaohua Li
2007-07-23 20:06 ` Jeff Dike
2007-07-24 5:22 ` Avi Kivity
2007-07-25 16:15 ` Jeff Dike
2007-07-25 17:12 ` [kvm-devel] " Carsten Otte
2007-07-23 23:10 ` Rusty Russell
2007-07-24 5:30 ` Avi Kivity
2007-07-24 6:11 ` Rusty Russell
2007-07-24 6:21 ` Avi Kivity
2007-07-24 6:45 ` Rusty Russell
2007-07-24 6:59 ` Avi Kivity
2007-07-24 7:17 ` Rusty Russell
2007-07-24 1:42 ` Shaohua Li
2007-07-24 5:42 ` 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=46A49F30.5010206@qumranet.com \
--to=avi@qumranet.com \
--cc=hch@infradead.org \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.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