From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org,
Philipp Psurek <philipp.psurek@gmail.com>
Subject: Re: [B.A.T.M.A.N.] Need some help to understand the code
Date: Tue, 05 Apr 2016 09:11:49 +0200 [thread overview]
Message-ID: <6462510.GtylGfypVS@bentobox> (raw)
In-Reply-To: <20160404231558.GG3002@otheros>
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
On Tuesday 05 April 2016 01:15:58 Linus Lüssing wrote:
> Maybe you could set up a KVM instance and play a little with its
> code in there? Try out lists and spinlocks etc. in there without
> crashing the VM instance :).
There is also an easy example how to build an amd64 [1] VM image with
many debug helpers enabled.
Kind regards,
Sven
[1] https://www.open-mesh.org/projects/open-mesh/wiki/Emulation_Debug
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-05 7:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 12:27 [B.A.T.M.A.N.] Need some help to understand the code Philipp Psurek
2016-04-02 6:15 ` Sven Eckelmann
2016-04-02 7:57 ` Philipp Psurek
2016-04-04 23:15 ` Linus Lüssing
2016-04-05 7:11 ` Sven Eckelmann [this message]
2016-04-05 7:36 ` Hans-Werner Hilse
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=6462510.GtylGfypVS@bentobox \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=philipp.psurek@gmail.com \
/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.