From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755443AbXGWMey (ORCPT ); Mon, 23 Jul 2007 08:34:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751355AbXGWMer (ORCPT ); Mon, 23 Jul 2007 08:34:47 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:46493 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751309AbXGWMeq (ORCPT ); Mon, 23 Jul 2007 08:34:46 -0400 Date: Mon, 23 Jul 2007 13:34:43 +0100 From: Christoph Hellwig To: Avi Kivity Cc: Christoph Hellwig , Shaohua Li , kvm-devel , lkml Subject: Re: [kvm-devel] [RFC 0/8]KVM: swap out guest pages Message-ID: <20070723123443.GB3674@infradead.org> Mail-Followup-To: Christoph Hellwig , Avi Kivity , Shaohua Li , kvm-devel , lkml References: <1185173489.2645.64.camel@sli10-conroe.sh.intel.com> <46A4829C.9080104@qumranet.com> <20070723122510.GA3674@infradead.org> <46A49F30.5010206@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46A49F30.5010206@qumranet.com> User-Agent: Mutt/1.4.2.3i X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 23, 2007 at 03:29:36PM +0300, Avi Kivity wrote: > >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. The patches in this thread. > Generic vmas will be more intrusive AFAICT. People use intrusive differently. Doing big changes to core code is not a problem if we actually get a proper interface. Just exporting core function without other changes and then writing code in modules that pokes into internals is much much worse. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [RFC 0/8]KVM: swap out guest pages Date: Mon, 23 Jul 2007 13:34:43 +0100 Message-ID: <20070723123443.GB3674@infradead.org> References: <1185173489.2645.64.camel@sli10-conroe.sh.intel.com> <46A4829C.9080104@qumranet.com> <20070723122510.GA3674@infradead.org> <46A49F30.5010206@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Christoph Hellwig , lkml , kvm-devel To: Avi Kivity Return-path: Content-Disposition: inline In-Reply-To: <46A49F30.5010206-atKUWr5tajBWk0Htik3J/w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org On Mon, Jul 23, 2007 at 03:29:36PM +0300, Avi Kivity wrote: > >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. The patches in this thread. > Generic vmas will be more intrusive AFAICT. People use intrusive differently. Doing big changes to core code is not a problem if we actually get a proper interface. Just exporting core function without other changes and then writing code in modules that pokes into internals is much much worse. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/