Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261657AbVADOHp (ORCPT ); Tue, 4 Jan 2005 09:07:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261656AbVADOHg (ORCPT ); Tue, 4 Jan 2005 09:07:36 -0500 Received: from mx1.redhat.com ([66.187.233.31]:233 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S261651AbVADOGm (ORCPT ); Tue, 4 Jan 2005 09:06:42 -0500 Date: Tue, 4 Jan 2005 09:06:24 -0500 (EST) From: Rik van Riel X-X-Sender: riel@chimarrao.boston.redhat.com To: Luke Kenneth Casson Leighton cc: Adam Heath , "linux-kernel@vger.kernel.org" , "xen-devel@lists.sf.net" Subject: Re: [Xen-devel] Re: [XEN] using shmfs for swapspace In-Reply-To: <20050104093044.GC10906@lkcl.net> Message-ID: References: <20050102162652.GA12268@lkcl.net> <20050103183133.GA19081@samarkand.rivenstone.net> <20050103205318.GD6631@lkcl.net> <20050104093044.GC10906@lkcl.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 804 Lines: 22 On Tue, 4 Jan 2005, Luke Kenneth Casson Leighton wrote: > then that tends to suggest that this is an issue that should > really be dealt with by XEN. Probably. > that there needs to be coordination of swap management between the > virtual machines. I'd like to see the maximum security separation possible between the unprivileged guests, though... -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/