All of lore.kernel.org
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Rob Landley <rob@landley.net>, Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Starting uml with the debugger
Date: Tue, 18 Oct 2005 03:58:17 +0200	[thread overview]
Message-ID: <200510180358.18434.blaisorblade@yahoo.it> (raw)
In-Reply-To: <200510172038.34803.rob@landley.net>

On Tuesday 18 October 2005 03:38, Rob Landley wrote:
> On Monday 17 October 2005 12:53, Jeff Dike wrote:
> > If this thing is new enough to have skas0, then just disable
> > CONFIG_MODE_TT and gdb it normally.

> I'm curious: now that skas0 mode works, when does tt mode start to go away?

I really don't want TT mode to go away.

Reason 1, developers need to be able to enable SMP. Or the locking will break 
even more. And in these two days, with the new (and better) lock debugging of 
2.6.14-rc (from Ingo), I've seen enough bugs to let me scared.

And I simply tested "uml_mconsole <umid> eth1=mcast".

Say, the uml_net_interrupt(), when holding the iface spinlock, can call, in 
the failure path, uml_net_close(), which calls the interrupt again.

Said that, I also have plans (from one year at least) to jail TT mode in a 
faster mode (i.e. with segment limits). I was descouraged, but the 
motivations behind that turned out to be mostly wrong (a supposed "bad 
performance"), and Xen uses it.

However, that's for the memory layout. For the rest I'd take normal SKAS flow. 
So, this would be a SKAS mode for everything, except that it would be like 
2.5G/1G instead of 3G/3G (if you know about 4G/4G in Fedora from Ingo vs. 
3G/1G in vanilla kernels, you should get what I mean. If not, search google 
or lwn.net about 4G/4G).

> (Obviously, making tls work might be nice first...)

I've been stopped by debugging problems, but now I workarounded GDB problems I 
can debug simple problems very easily.

TLS is more difficult, as you need to disassemble the faulting location for 
the strange SIGSEGV, and that is not even always possible.

However, for your Ubuntu issue, see the mail I'm going to post.
> Rob

-- 
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! Messenger: chiamate gratuite in tutto il mondo 
http://it.messenger.yahoo.com



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      reply	other threads:[~2005-10-18  1:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-17 17:09 [uml-devel] Starting uml with the debugger Etay Meiri
2005-10-17 17:53 ` Jeff Dike
2005-10-17 18:23   ` Etay Meiri
2005-10-17 19:05     ` Henrik Nordstrom
2005-10-18  1:38   ` Rob Landley
2005-10-18  1:58     ` Blaisorblade [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=200510180358.18434.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=jdike@addtoit.com \
    --cc=rob@landley.net \
    --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 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.