From: Steven Rostedt <rostedt@goodmis.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: virtualization@lists.osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] lguest32 kallsyms backtrace of guest.
Date: Wed, 04 Apr 2007 23:19:57 -0400 [thread overview]
Message-ID: <1175743197.9371.39.camel@localhost.localdomain> (raw)
In-Reply-To: <1175741652.12230.620.camel@localhost.localdomain>
On Thu, 2007-04-05 at 12:54 +1000, Rusty Russell wrote:
>
> This is a cool idea, but there are two issues with this patch. The
> first is that it's 500 lines of code: that's around +10% on lguest's
> total code size! The second is that it conflicts with the medium-term
> plan to allow any user to run up lguests: this is why lg.ko never
> printk()s about problems with the guest.
Not much I can do about the size, but it's in the debug section so
hopefully it's not considered too bad :)
>
> While it is useful for cases where a guest dies mysteriously before it
> brings up the console, three alternatives come to mind:
>
> 1) Modify early_printk so Guests can use it.
> 2) Have a separate tool(-set?) for this kind of post-mortem. Then you
> just have to implement guest suspend! 8)
> 3) Put this in a CONFIG_LGUEST_DEBUG.
>
> Note that options 1 or 2 make you do more work, but are probably better
> in the long term. I'm happy for #3 to sit as a patch in the tree for
> the duration, tho!
OK, I'll make a #3 patch to send, but the #1 looks best. Not to mention
that I still need to make it so that the console can read it.
-- Steve
prev parent reply other threads:[~2007-04-05 3:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 18:23 [PATCH] lguest32 kallsyms backtrace of guest Steven Rostedt
2007-04-05 2:54 ` Rusty Russell
2007-04-05 3:19 ` Steven Rostedt [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=1175743197.9371.39.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).