From: Sasha Levin <levinsasha928@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: penberg@kernel.org, kvm@vger.kernel.org, mingo@elte.hu,
asias.hejun@gmail.com, gorcunov@gmail.com
Subject: Re: [PATCH 2/2] kvm tools: Allow easily sandboxing applications within a guest
Date: Sun, 04 Dec 2011 14:11:30 +0200 [thread overview]
Message-ID: <1323000690.4205.3.camel@lappy> (raw)
In-Reply-To: <4EDB4AAA.8090203@redhat.com>
On Sun, 2011-12-04 at 12:25 +0200, Avi Kivity wrote:
> 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.
Yup, it makes bisecting most issues which are reproducible pretty easy.
Yesterday I've managed to bisect the issue in '[BUG] net: kernel BUG at
include/net/netns/generic.h:40!' without having to touch the process
once. Obviously I was pretty happy :)
--
Sasha.
prev parent reply other threads:[~2011-12-04 12:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 7:16 [PATCH 1/2] kvm tools: Remove double 'init=' kernel param Sasha Levin
2011-12-02 7:16 ` [PATCH 2/2] kvm tools: Allow easily sandboxing applications within a guest Sasha Levin
2011-12-02 7:26 ` Pekka Enberg
2011-12-02 7:35 ` Sasha Levin
2011-12-02 7:39 ` Pekka Enberg
2011-12-02 7:44 ` Sasha Levin
2011-12-02 7:47 ` Pekka Enberg
2011-12-04 10:25 ` Avi Kivity
2011-12-04 12:11 ` Sasha Levin [this message]
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=1323000690.4205.3.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=avi@redhat.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.