linux-um archives
 help / color / mirror / Atom feed
From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux devel
	<user-mode-linux-devel@lists.sourceforge.net>,
	BlaisorBlade <blaisorblade_spam@yahoo.it>
Subject: [uml-devel] Re: Some changes in SKAS0
Date: Tue, 13 Sep 2005 15:17:48 +0200	[thread overview]
Message-ID: <4326D17C.5010402@fujitsu-siemens.com> (raw)
In-Reply-To: <20050812170900.GC7448@ccure.user-mode-linux.org>

Jeff Dike wrote:
> From our discussion yesterday, ...
> 
> On Fri, Jul 15, 2005 at 05:36:34PM +0200, Bodo Stroesser wrote:
> 
>>So I thought about avoiding the sigreturn at all. Working on
>>this I found out some small points:
> 
> 
> I kept this patch
> 
> 
>>- there is a bug (typo) in wait_stub_done()
> 
> 
> but dropped these two, plus my dont-save-fpregs patch.  Correct?
> 
> 
>>- stopping stub_segv_handler with a "breakpoint" without
>>  calling sigreturn, lets SIGSEGV being blocked after that.
>>  At the next SIGSEGV, I see stub_wait_done() calling panic
>>  just as with Rob's problem. And I see the child being gone!
>>  I understand, that the host unblocks SIGSEGV and sets the
>>  handler to SIG_DFL. But I don't understand, why the child
>>  already is gone after the waitpid(), without resuming it.
>>  I guess, this is the reason for Rob not being able to debug
>>  the problem.
>>  Thus I added SA_NOMASK to the flags for the handler.
>>
>>- I changed the additional mask for the handler to be empty.
>>  The only exception is x86_64, that currently must use sigreturn
>>  and therefore still masks SIGUSR1 while the handler runs.
>>  In skas, userspace shouldn't receive SIGIO or SIGWINCH (I hope
>>  I'm right here?), SIGVTALRM already is handled by wait_stub_done.
>>  Then I changed i386's stub_segv_handler to stop using "int3"
>>  immediately after saving faultinfo.
>>  This new method saves some syscalls on i386 and s390 and
>>  simplifies s390.
> 
> 
> 				Jeff
Sorry, late reply: you are right.

	Bodo


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      reply	other threads:[~2005-09-13 13:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-15 15:36 [uml-devel] Some changes in SKAS0 Bodo Stroesser
2005-07-15 20:47 ` [uml-devel] " Jeff Dike
2005-07-30 15:54 ` Jeff Dike
2005-08-05 11:43   ` Bodo Stroesser
2005-08-12 17:09 ` Jeff Dike
2005-09-13 13:17   ` Bodo Stroesser [this message]

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=4326D17C.5010402@fujitsu-siemens.com \
    --to=bstroesser@fujitsu-siemens.com \
    --cc=blaisorblade_spam@yahoo.it \
    --cc=jdike@addtoit.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