From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Garzik <jgarzik@pobox.com>, Jeff Dike <jdike@addtoit.com>,
linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] Current state of UML - some help needed from mainline.
Date: Tue, 7 Sep 2004 20:13:49 +0200 [thread overview]
Message-ID: <200409072013.49494.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200409061956.34557.blaisorblade_spam@yahoo.it>
For LKML: I'm not subscribed, so don't forget to CC me.
On Monday 06 September 2004 19:56, BlaisorBlade wrote:
> On Sunday 05 September 2004 22:28, Jeff Garzik wrote:
> > Overall I am really impressed. Like other arches in the Linux kernel,
> > it is IMO very important to be able to work "out of the box", without
> > patches.
Yes - especially when microAPI changes happen every day, as of 2.6. I've just
downloaded a snapshot including the merge, so I'll be able to merge some
little fixes which have happened since.
Do you think that keeping a UML tree for new, experimental features is a good
idea, or that this role should go to -mm?
I ask this also because I don't know how much would help general review for
new features.
For instance, the "hostfs" feature is in the middle of a rewrite and the new
code is still very broken (the current release says more or less "VFS: busy
inodes after unmount - self destroying in 5 seconds. Have a nice day", but
maybe this is fixed; plus has a number of other bugs).
Also, SMP hasn't compiled for a while, so there is a number of locking problem
- at least one straight deadlock in the ubd driver when passing ubd=sync.
It's not a hard problem - just not yet fixed it.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
WARNING: multiple messages have this Message-ID (diff)
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Garzik <jgarzik@pobox.com>, Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] Current state of UML - some help needed from mainline.
Date: Tue, 7 Sep 2004 20:13:49 +0200 [thread overview]
Message-ID: <200409072013.49494.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200409061956.34557.blaisorblade_spam@yahoo.it>
For LKML: I'm not subscribed, so don't forget to CC me.
On Monday 06 September 2004 19:56, BlaisorBlade wrote:
> On Sunday 05 September 2004 22:28, Jeff Garzik wrote:
> > Overall I am really impressed. Like other arches in the Linux kernel,
> > it is IMO very important to be able to work "out of the box", without
> > patches.
Yes - especially when microAPI changes happen every day, as of 2.6. I've just
downloaded a snapshot including the merge, so I'll be able to merge some
little fixes which have happened since.
Do you think that keeping a UML tree for new, experimental features is a good
idea, or that this role should go to -mm?
I ask this also because I don't know how much would help general review for
new features.
For instance, the "hostfs" feature is in the middle of a rewrite and the new
code is still very broken (the current release says more or less "VFS: busy
inodes after unmount - self destroying in 5 seconds. Have a nice day", but
maybe this is fixed; plus has a number of other bugs).
Also, SMP hasn't compiled for a while, so there is a number of locking problem
- at least one straight deadlock in the ubd driver when passing ubd=sync.
It's not a hard problem - just not yet fixed it.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
next prev parent reply other threads:[~2004-09-07 18:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 3:00 [uml-devel] uml-patch-2.6.7-2 Jeff Dike
2004-08-19 3:00 ` uml-patch-2.6.7-2 Jeff Dike
2004-08-27 7:10 ` [uml-devel] uml-patch-2.6.7-2 Werner Almesberger
2004-09-05 19:35 ` BlaisorBlade
2004-09-08 23:15 ` Jeff Dike
2004-09-05 15:35 ` BlaisorBlade
2004-09-05 20:28 ` [uml-devel] Current state of UML Jeff Garzik
2004-09-06 17:56 ` BlaisorBlade
2004-09-07 4:40 ` Jeff Garzik
2004-09-07 5:05 ` Adam Heath
2004-09-07 5:13 ` Jeff Garzik
2004-09-07 5:39 ` Adam Heath
2004-09-07 18:13 ` BlaisorBlade [this message]
2004-09-07 18:13 ` [uml-devel] Current state of UML - some help needed from mainline BlaisorBlade
2004-09-09 5:30 ` Jeff Garzik
2004-09-09 5:30 ` Jeff Garzik
2004-09-08 20:40 ` [uml-devel] Re: Current state of UML Jeff Dike
2004-09-09 0:35 ` [uml-devel] uml-patch-2.6.7-2 Jeff Dike
2004-09-09 0:35 ` Jeff Dike
2004-09-11 14:41 ` BlaisorBlade
2004-09-11 14:41 ` BlaisorBlade
2004-09-07 21:16 ` [uml-devel] Compiling UML 2.6.8.1 with Static Linking results in segfault Michael Ralston
2004-09-08 0:18 ` Jeff Dike
2004-09-07 23:57 ` Michael Ralston
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=200409072013.49494.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--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.