From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>, Allan Graves <allan.graves@oracle.com>
Subject: Re: [uml-devel] stack and scheduler patches
Date: Sun, 4 Sep 2005 13:51:32 +0200 [thread overview]
Message-ID: <200509041351.32837.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050902165935.GA6651@ccure.user-mode-linux.org>
On Friday 02 September 2005 18:59, Jeff Dike wrote:
> On Wed, Aug 31, 2005 at 07:06:33PM -0400, Allan Graves wrote:
> > Jeff,
> > Here's the patches. Hope these meet your approval!
Could you please write a proper changelog? Reading a patch is possible, but
needs time which I don't have in the very moment.
Also, what is the difference between your "stack trace" patch, which adds a
member to thread_struct, for each process, so I'd like a minimum of
justification, and one of the sysrq options which does exactly this?
Apart that the second is currently buggy, and is global, as in what you plan
here:
/* Would be nice:
+ 1) Send showregs output to mconsole.
+ 2) Add a way to stack dump all pids.
+ */
Sorry if these questions seem bad - but that's why changelogs are used.
> > Allan
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-09-04 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 23:06 [uml-devel] stack and scheduler patches Allan Graves
2005-09-02 16:59 ` Jeff Dike
2005-09-04 11:51 ` Blaisorblade [this message]
2005-09-06 15:37 ` Jeff Dike
2005-09-06 16:10 ` [uml-devel] sched and stack patch changelogs Allan Graves
2005-09-06 15:46 ` [uml-devel] stack and scheduler patches Allan Graves
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=200509041351.32837.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=allan.graves@oracle.com \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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