linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: Re: [uml-devel] Recent patches of note
Date: Thu, 16 Jun 2005 20:35:16 -0400	[thread overview]
Message-ID: <20050617003516.GA12344@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200506162009.35357.blaisorblade@yahoo.it>

On Thu, Jun 16, 2005 at 08:09:34PM +0200, Blaisorblade wrote:
> +struct task_struct;
> +extern void arch_switch(struct task_struct *from, struct task_struct *to);

Is the task_struct; needed, considering that there is get_task returning
one a few lines higher?

> +	/* XXX: This is bogus, it's already done in local_irq_enable. Or does
> +	 * ordering matters? */

No, my signal handler initialization is confused and redundant in places.
Just fix that and resend.

> Fix the do_fork calling convention: normal arch pass the regs and the new sp
> value to do_fork instead of NULL.
> 
> Currently the arch-independent code ignores these values, while the UML code   
> (actually it's copy_thread) gets the right values by itself.
> 
> With this patch, things are fixed up.
>     
> Low-priority.

But long-overdue.  This one is applied.



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&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

  parent reply	other threads:[~2005-06-17  2:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16 16:07 [uml-devel] Recent patches of note Jeff Dike
2005-06-16 17:36 ` Bodo Stroesser
2005-06-16 17:47   ` Jeff Dike
2005-06-16 17:55     ` Bodo Stroesser
2005-06-16 18:02       ` Bodo Stroesser
2005-06-16 18:09       ` Blaisorblade
2005-06-16 18:31         ` Bodo Stroesser
2005-06-16 18:41           ` Blaisorblade
2005-06-16 18:40             ` Bodo Stroesser
2005-06-16 18:51               ` Blaisorblade
2005-06-16 22:23                 ` Jeff Dike
2005-06-17  9:09                   ` Bodo Stroesser
2005-06-17 18:36                   ` Blaisorblade
2005-06-17  0:35         ` Jeff Dike [this message]
2005-06-17 18:40           ` Blaisorblade
     [not found] <s2b18c1b.063@ORANGE.OUS.EDU>
2005-06-16 22:13 ` Jeff Dike
  -- strict thread matches above, loose matches on Subject: below --
2005-06-16 22:59 Anthony Brock
     [not found] <s2b1a1ed.010@ORANGE.OUS.EDU>
2005-06-20 14:47 ` Jeff Dike
     [not found] <s2b19c99.097@ORANGE.OUS.EDU>
2005-06-20 14:53 ` Jeff Dike
2005-06-20 17:59   ` William Stearns
2005-06-20 21:31     ` Blaisorblade
     [not found] <s2b6982e.048@ORANGE.OUS.EDU>
2005-06-20 20:11 ` Jeff Dike

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=20050617003516.GA12344@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=blaisorblade@yahoo.it \
    --cc=bstroesser@fujitsu-siemens.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