From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: Jeff Dike <jdike@addtoit.com>,
user-mode-linux devel
<user-mode-linux-devel@lists.sourceforge.net>,
Gerd Knorr <kraxel@bytesex.org>
Subject: [uml-devel] Re: UML running on a SMP host: bug in SKAS3 patch
Date: Thu, 27 Jan 2005 13:42:33 +0100 [thread overview]
Message-ID: <41F8E1B9.9000903@fujitsu-siemens.com> (raw)
In-Reply-To: <200501262213.32396.blaisorblade@yahoo.it>
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
Blaisorblade wrote:
> I've not seen any update to them from their original version (i.e. when they
> were first discussed). Is this correct?
I guess, you're talking about my SYSEMU_SINGLESTEP patches. Since I created two
patches each for 2.6.9 and 2.6.7, you should have these four patches:
../tmp/patch-2.6.7-skas-v7-reorganize
../tmp/patch-2.6.7-skas-v7-add-SYSEMU_SINGLESTEP
../tmp/patch-2.6.9-skas-v7-reorganize
../tmp/patch-2.6.9-skas-v7-add-SYSEMU_SINGLESTEP
On my system, the change date is Nov 12. So, I guess the ones you have still
are up to date.
But on my 2.6.9, I added a further patch to catch some rare conditions, when
doing sysaudit together with ptracing, or switching between different ptrace
commands.
I don't know, if I ever sent it to the list. IIRC, uml runs fine without it
(but IMHO, we should use the more "complete" solution).
The sysaudit/ptrace issue is a general problem for i386, too.
Have attached a tarball containing all five patches.
Bodo
[-- Attachment #2: sysemu-singlestep.tar --]
[-- Type: application/x-tar, Size: 30720 bytes --]
prev parent reply other threads:[~2005-01-27 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 16:46 [uml-devel] UML running on a SMP host: bug in SKAS3 patch Bodo Stroesser
2005-01-26 21:13 ` [uml-devel] " Blaisorblade
2005-01-27 12:42 ` 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=41F8E1B9.9000903@fujitsu-siemens.com \
--to=bstroesser@fujitsu-siemens.com \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=kraxel@bytesex.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