From: Blaisorblade <blaisorblade@yahoo.it>
To: akpm@osdl.org, jdike@addtoit.com, bstroesser@fujitsu-siemens.com,
linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net,
blaisorblade@yahoo.it
Subject: [uml-devel] [patch 0/7] uml: some invasive changes for -mm
Date: Sun, 24 Apr 2005 20:39:55 +0200 [thread overview]
Message-ID: <200504242039.57025.blaisorblade@yahoo.it> (raw)
This is the first of a series of 7 invasive patches for the -mm tree, which
are to be reviewed (not only by UML folks), and possibly merged for the
2.6.13 cycle.
The first one splits the i386 syscall table out of entry.S, without any real
change for them (the file is included in the old place); if there are any
syscall table changes, please be careful; this maybe means place *this* one
before the others (or even merge now the i386 code movement part); I don't
want that this patch is modified and that subtle bugs are introduced. The
code movement is a really trivial code movement, however (no hidden changes).
This is needed to enable us to include the i386 syscall table, so that we are
sure that they match. I already handled the real differences between i386 and
UML (see the patch).
uml-fix-syscall-table-i386.patch
uml: fix syscall table by including $(SUBARCH)'s one, for i386
uml-quick-fix-syscall-table-x86_64.patch
uml: quick fix syscall table for x86_64
uml-fix-syscall-table-rem-for-x86-64.patch
uml: fix syscall table by including $(SUBARCH)'s one, for x86-64
uml-console-redo-locking.patch
uml: redo console locking
[ It's invasive, but seems to work well; wide testing is needed ]
uml-hostfs-avoid-buffers.patch
uml - hostfs: avoid buffers
[ This is something which should work, even because you said that; I've
partially verified this myself ]
uml-commentary-about-forking-flag.patch
uml: commentary about forking flag
[ Jeff, give a look and possibly correct it. ]
uml-ubd-handle-readonly.patch
uml ubd: handle readonly status
[ I cc'ed Jens Axboe ]
They are not to be confused with the previous series of 6 patches I also sent
today, which are mostly little or already tested patches (list below); the
explicitly marked one are urgent for 2.6.12, while for the other just take
your choice (they should be trivial and have been tested):
[LIST of patches TO MERGE]:
uml-workaround-sed-behaviour.patch
uml: workaround old problematic sed behaviour [compile-fix, for 2.6.12]
uml-nfsd-syscall.patch
uml: add nfsd syscall when nfsd is modular [for 2.6.12]
uml-crypto-i586.patch
uml: support AES i586 crypto driver [for 2.6.12]
uml-Makefile-avoid-rebuild.patch
uml kbuild: avoid useless rebuilds [for 2.6.13]
uml-inline-empty.patch
uml: inline empty proc
uml-move-va-copy-conditional.patch
uml: move va_copy conditional def
Thanks a lot for the attention and regards.
--
Paolo Giarrusso, aka Blaisorblade
Skype user "PaoloGiarrusso"
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&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
next reply other threads:[~2005-04-24 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-24 18:39 Blaisorblade [this message]
2005-04-25 15:15 ` [uml-devel] Re: [patch 0/7] uml: some invasive changes for -mm Bodo Stroesser
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=200504242039.57025.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=akpm@osdl.org \
--cc=bstroesser@fujitsu-siemens.com \
--cc=jdike@addtoit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox