linux-um archives
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Cc: Blaisorblade <blaisorblade_spam@yahoo.it>,
	jdike@addtoit.com, user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: [patch 1/1] SYSEMU: avoid intercepting syscall on return when using SYSCALL again.
Date: Fri, 29 Oct 2004 09:51:25 +0200	[thread overview]
Message-ID: <20041029075124.GA14311@bytesex> (raw)
In-Reply-To: <41819A8A.20403@fujitsu-siemens.com>

> Here's the patch:

Hmm, your mailer seems to mangle whitespaces, I often can apply your
patches mailed inline with "patch -l" only (the mime attached ones are
fine).

Two small fixes I need in the big stack of patches i have now to
build kernels successfully.  The first is a simple missing include:

==============================[ cut here ]==============================
--- linux-uml-2.6.9.orig/arch/um/os-Linux/signal.c	2004-10-28 20:11:02.757586671 +0200
+++ linux-uml-2.6.9/arch/um/os-Linux/signal.c	2004-10-28 20:23:32.730183963 +0200
@@ -6,6 +6,7 @@
 #include <signal.h>
 #include "time_user.h"
 #include "mode.h"
+#include "choose-mode.h"
 #include "sysdep/signal.h"
 
 void sig_handler(int sig)
==============================[ cut here ]==============================

The second one is a fixup for the host-skas3 patch.  That one is needed
if you use one source tree for both host and uml builds.  Without that
fixup the host-skas3 patch breaks uml kernel builds (and also all other
architectures as only i386 has sysemu right now ...).

==============================[ cut here ]==============================
--- uml-2.6.9-rc2.orig/arch/um/include/skas_ptrace.h	2004-09-16 16:10:16.000000000 +0200
+++ uml-2.6.9-rc2/arch/um/include/skas_ptrace.h	2004-09-16 16:10:24.000000000 +0200
@@ -6,6 +6,7 @@
 #ifndef __SKAS_PTRACE_H
 #define __SKAS_PTRACE_H
 
+#ifndef PTRACE_FAULTINFO
 struct ptrace_faultinfo {
 	int is_write;
 	unsigned long addr;
@@ -21,6 +22,7 @@ struct ptrace_ldt {
 #define PTRACE_SIGPENDING 53
 #define PTRACE_LDT 54
 #define PTRACE_SWITCH_MM 55
+#endif
 
 #endif
 
--- uml-2.6.9-rc2.orig/kernel/fork.c	2004-09-16 16:10:21.000000000 +0200
+++ uml-2.6.9-rc2/kernel/fork.c	2004-09-16 16:12:40.000000000 +0200
@@ -1038,7 +1038,9 @@ static task_t *copy_process(unsigned lon
 	 * of CLONE_PTRACE.
 	 */
 	clear_tsk_thread_flag(p, TIF_SYSCALL_TRACE);
+#ifdef TIF_SYSCALL_EMU
 	clear_tsk_thread_flag(p, TIF_SYSCALL_EMU);
+#endif
 
 	/* Our parent execution domain becomes current domain
 	   These must match for thread signalling to apply */
==============================[ cut here ]==============================

It's kida quick&dirty, the real fix probably would be to have the skas
ptrace stuff in *one* place, guess that isn't going to happen before
skas is merged mainline through.  Whats the status on skas4 btw.?

  Gerd



-------------------------------------------------------
This Newsletter Sponsored by: Macrovision 
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate 
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
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:[~2004-10-29  8:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-21 23:18 [uml-devel] [patch 1/1] SYSEMU: avoid intercepting syscall on return when using SYSCALL again blaisorblade_spam
2004-10-22  0:37 ` BlaisorBlade
2004-10-22  9:22 ` [uml-devel] " Bodo Stroesser
2004-10-22 16:14   ` BlaisorBlade
2004-10-22 16:23     ` Bodo Stroesser
2004-10-27 14:21       ` Bodo Stroesser
2004-10-28 23:04         ` Blaisorblade
2004-10-28 23:36           ` Bodo Stroesser
     [not found]             ` <200410290200.46907.blaisorblade_spam@yahoo.it>
2004-10-29  1:19               ` Bodo Stroesser
2004-10-29  7:51                 ` Gerd Knorr [this message]
2004-10-29 13:09                   ` Blaisorblade

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=20041029075124.GA14311@bytesex \
    --to=kraxel@bytesex.org \
    --cc=blaisorblade_spam@yahoo.it \
    --cc=bstroesser@fujitsu-siemens.com \
    --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