From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 2/2] kvm tools: Allow easily sandboxing applications within a guest Date: Sun, 04 Dec 2011 12:25:46 +0200 Message-ID: <4EDB4AAA.8090203@redhat.com> References: <1322810215-9647-1-git-send-email-levinsasha928@gmail.com> <1322810215-9647-2-git-send-email-levinsasha928@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: penberg@kernel.org, kvm@vger.kernel.org, mingo@elte.hu, asias.hejun@gmail.com, gorcunov@gmail.com To: Sasha Levin Return-path: Received: from mx1.redhat.com ([209.132.183.28]:49533 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752694Ab1LDK0B (ORCPT ); Sun, 4 Dec 2011 05:26:01 -0500 In-Reply-To: <1322810215-9647-2-git-send-email-levinsasha928@gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: On 12/02/2011 09:16 AM, Sasha Levin wrote: > This is useful when testing code that might cause problems on the host, or > to automate kernel testing since it's now easy to link a kvm tools test > script with 'git bisect run'. This tie-up into git bisect is a really cool idea. With device assignment, you can even bisect driver bugs this way. -- error compiling committee.c: too many arguments to function