linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: Re: [uml-devel] Review needed for ubd fixes
Date: Wed, 28 Sep 2005 18:47:20 +0200	[thread overview]
Message-ID: <200509281847.21078.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050928155405.GA12888@ccure.user-mode-linux.org>

On Wednesday 28 September 2005 17:54, Jeff Dike wrote:
> On Wed, Sep 28, 2005 at 02:14:32PM +0200, Blaisorblade wrote:
> > Very, very nice.

> > Let's hope for the better, but next time the debug should be done
> > *before* merging, ok? Even because, for instance, if (say) the patch was
> > ready for 2.6.14 and merged into 2.6.15, I could have released a test
> > tree against 2.6.14 (maybe I could do this now).

> I thought I did.  AIO had been in my tree forever with no apparent
> problems.
We're not currently getting a lot of testing on that. Apart the really current 
issue of the page not uptodate, users mostly ran that because of x86_64 
support, which is now reliable in mainline.

In fact, the SKAS0 compiler-dependant bug (the asm code was popping a fixed 
number of words, which was wrong with different compiler) only came out on 
the tree I released against 2.6.12...
> I recently started running 24 hour/day stress tests on UML, and 
> that turned up some problems.  People turning on spinlock debugging turned
> up the sleeping while atomic problem.  And me staring at the code as a
> result of that turned up the possible deadlock.

> > And ask Jens Axboe if it can give a look to them (this time it's less
> > necessary, since there are less dirty tricks).

> Yeah.  This still needs some work.  I need to deal with the bitmap array
> properly.

> 				Jeff

-- 
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-09-28 16:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-17 22:45 [uml-devel] Review needed for ubd fixes Jeff Dike
2005-09-20 12:01 ` Blaisorblade
2005-09-20 19:06   ` Jeff Dike
2005-09-21 15:49     ` Blaisorblade
2005-09-21 18:04       ` Jeff Dike
2005-09-21 19:06         ` Blaisorblade
2005-09-21 20:45           ` Jeff Dike
2005-09-22 20:51             ` Blaisorblade
2005-09-27 18:12               ` Jeff Dike
2005-09-28 12:14                 ` Blaisorblade
2005-09-28 15:54                   ` Jeff Dike
2005-09-28 16:47                     ` 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=200509281847.21078.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=bstroesser@fujitsu-siemens.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