From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: akpm@osdl.org, jdike@addtoit.com, linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [patch 0/7] uml: some invasive changes for -mm
Date: Mon, 25 Apr 2005 17:15:59 +0200 [thread overview]
Message-ID: <426D09AF.6030209@fujitsu-siemens.com> (raw)
In-Reply-To: <200504242039.57025.blaisorblade@yahoo.it>
Blaisorblade wrote:
> 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).
I love this idea and it fits well to UML/s390, where syscall table already
lives in a separate source.
As change and grow of syscall tables is not really coordinated between different
arches, this change will simplify maintenance of UML-subarches a lot.
Bodo
-------------------------------------------------------
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
WARNING: multiple messages have this Message-ID (diff)
From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: akpm@osdl.org, jdike@addtoit.com, linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [patch 0/7] uml: some invasive changes for -mm
Date: Mon, 25 Apr 2005 17:15:59 +0200 [thread overview]
Message-ID: <426D09AF.6030209@fujitsu-siemens.com> (raw)
In-Reply-To: <200504242039.57025.blaisorblade@yahoo.it>
Blaisorblade wrote:
> 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).
I love this idea and it fits well to UML/s390, where syscall table already
lives in a separate source.
As change and grow of syscall tables is not really coordinated between different
arches, this change will simplify maintenance of UML-subarches a lot.
Bodo
next prev parent reply other threads:[~2005-04-25 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-24 18:39 [uml-devel] [patch 0/7] uml: some invasive changes for -mm Blaisorblade
2005-04-24 18:39 ` Blaisorblade
2005-04-25 15:15 ` Bodo Stroesser [this message]
2005-04-25 15:15 ` 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=426D09AF.6030209@fujitsu-siemens.com \
--to=bstroesser@fujitsu-siemens.com \
--cc=akpm@osdl.org \
--cc=blaisorblade@yahoo.it \
--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 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.