From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756826Ab1EZLMG (ORCPT ); Thu, 26 May 2011 07:12:06 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:52271 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752893Ab1EZLMF (ORCPT ); Thu, 26 May 2011 07:12:05 -0400 Date: Thu, 26 May 2011 13:11:27 +0200 From: Ingo Molnar To: Gleb Natapov Cc: Pekka Enberg , Avi Kivity , James Morris , Linus Torvalds , Kees Cook , Thomas Gleixner , Peter Zijlstra , Will Drewry , Steven Rostedt , linux-kernel@vger.kernel.org, Chris Wright , Pekka Enberg Subject: Re: [PATCH 3/5] v2 seccomp_filters: Enable ftrace-based system call filtering Message-ID: <20110526111127.GF1763@elte.hu> References: <20110525180100.GY19633@outflux.net> <20110526082451.GB26775@elte.hu> <4DDE1419.3000708@redhat.com> <20110526085939.GG29458@redhat.com> <20110526103836.GC1763@elte.hu> <20110526104636.GL29458@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110526104636.GL29458@redhat.com> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.3.1 -2.0 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Gleb Natapov wrote: > > In that model each process has its own stack, not accessible to > > other worker processes. They'd only share the guest RAM image and > > some (minimal) global state. > > > > This way the individual devices are (optionally) isolated from > > each other. In a way this is a microkernel done right ;-) > > But doesn't this design suffer the same problem as microkernel? > Namely a lot of slow IPCs? Most of the IPCs we do already, to keep the devices separated from each other. So the most common type of IPC comes 'for free' in that model - and this is specific to virtualization so i'd not extend the claim to the host kernel. virtio is an IPC mechanism to begin with. It's certainly not entirely free though so if this is implemented in tools/kvm/ it should be configurable. Thanks, Ingo