linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Gerd Knorr <kraxel@bytesex.org>,
	Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Ported SKAS3-v7 (and partially -V8) for 2.6.11. Uncleanness about SYSEMU_SINGLESTEP
Date: Thu, 10 Feb 2005 13:43:29 +0100	[thread overview]
Message-ID: <200502101343.30345.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050209173336.GE14590@bytesex>

On Wednesday 09 February 2005 18:33, Gerd Knorr wrote:
> > > Anyone looked at 2.6.11-rc1 for the host?  Some more ptrace cleanups
> >
> > I've already solved those conflict earlier on -rc1 (not tested) but I
> > didn't polish it out yet... if you are in a hurry, I can finish it and
> > post the result today on the ML. If not, I'll publish it later.
>
> Was busy with other stuff recently, but next days I plan to look at this
> again.  I've seen you released skas v8 meanwhile, but for 2.6.9 only.
> If you have a 2.6.11-rc patch as well already that would be very nice.
I've just done a -V7 for -rc3-bk6... I've called it -V7-rc1 because 
potentially something could go wrong (in general, and for this special 
kernel).

I've also added three patches from the V8-rc1 for 2.6.9 (so it's actually a 
-V7a: versioning is fscking up). I've not yet added the SYSEMU_SINGLESTEP 
support, because it seemed me a bit unclean even in 2.6.9, so even porting it 
cleanly to 2.6.10 is a bit hard (C. Aker did the porting, and , but in that 
form it is not up-to-date with the introduction of the set/clear_singlestep 
accessors).

The problem is that PTRACE_SYSEMU_SINGLESTEP is put together with 
PTRACE_SYSCALL, not with PTRACE_SINGLESTEP... I understand in 2.6.7 it maybe 
made sense (SINGLESTEP had a different behaviour then, problems when 
singlestepping syscalls) but it's unclean in 2.6.9 and does not port well to 
2.6.10, as said (... unless I miss something, I'm going to cleanup this for 
2.6.9 and for 2.6.10.

For 2.6.7 I would rawly use your version, unless I discovered any bugs during 
the cleanup (backporting cleanups is useless IMHO, unless for other reasons 
like keeping things in sync).
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade




-------------------------------------------------------
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

      parent reply	other threads:[~2005-02-10 12:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21 12:15 [uml-devel] 2.6.11-rc1 Gerd Knorr
2005-01-21 13:07 ` Blaisorblade
2005-01-29 23:34   ` Anthony Brock
     [not found]   ` <20050209173336.GE14590@bytesex>
2005-02-10 12:43     ` Blaisorblade [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=200502101343.30345.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=bstroesser@fujitsu-siemens.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