From: Blaisorblade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Gerd Knorr <kraxel@bytesex.org>
Subject: Re: [uml-devel] Merging some of your patches
Date: Tue, 30 Nov 2004 20:03:07 +0100 [thread overview]
Message-ID: <200411302003.08104.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200411301945.07814.blaisorblade_spam@yahoo.it>
On Tuesday 30 November 2004 19:45, Blaisorblade wrote:
> Since you've started sending UML patches, I've remembered to ask you this.
>
> In particular, from a general feeling, you should merge:
>
> uml-fix-umldir-order
>
> uml-fix-export-symbol if not already applied.
>
> uml-raise-tty-limit (maybe something similar could be good for ubd, too? We
> are using half of the 256 minors available).
Forgot some other ones:
uml-core-on-panic - I remember it being a bit controversial.
At least it has been turned to using the notifier_chain... which was problem
#1. #2 was that you need to skip all the rest of exit cleanup, which Jeff
didn't like... but as long as it is not a change to the default behaviour, I
think he might accept it.
uml-general-protection-fault - from the comment, it seems that if that were a
page fault, it would be fixable, while we always prefer to guess it's a GFP
and so to die horribly. If this is true, it cannot be merged.
But what about adding a PTRACE_EX_FAULTINFO to SKAS3 and probe for it at
startup? Jeff Dike wanted to wait for SKAS4 to fix it, but as you see SKAS3
is still under very active development. Also, we get all the possible
compatibility we could, this way.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
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:[~2004-11-30 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 18:45 [uml-devel] Merging some of your patches Blaisorblade
2004-11-30 19:03 ` Blaisorblade [this message]
[not found] ` <20041202114819.GA31396@bytesex>
2004-12-04 3:58 ` Blaisorblade
2004-12-07 12:03 ` Gerd Knorr
2004-12-10 18:51 ` SKAS4 future and present (was: Re: [uml-devel] Merging some of your patches) Blaisorblade
2004-12-10 22:46 ` Gerd Knorr
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=200411302003.08104.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=kraxel@bytesex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox