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,
	"Charles P. Wright" <cwright@cs.sunysb.edu>,
	Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: Re: [uml-devel] SYSEMU getting merged - but I'm in doubt
Date: Tue, 6 Sep 2005 12:10:32 -0400	[thread overview]
Message-ID: <20050906161032.GA6157@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200509041702.18506.blaisorblade@yahoo.it>

On Sun, Sep 04, 2005 at 05:02:18PM +0200, Blaisorblade wrote:
> Now, the point is: should I ask Linus to drop it for now, clean the 
> interface, and resend the cleaned up one, with different ptrace call codes?

I would be tempted to leave it in and fix it before 2.6.14.  We need different
ptrace codes so that UML knows how to switch interception types, I take it?

UML is the only user, so there aren't really any compatibility issues.

> On the host side, instead, supporting both the broken API and the new one is 
> more difficult.

Yeah, and it shouldn't be done.  This is one reason I'd like to use the same
ptrace codes - it doesn't leave a hole in the codes that says there was a 
broken ABI there once.

> What's your opinion on this? The options are:
> 1) merge it as-is
> 2) take it back for now, fix it and merge it for 2.6.15.

Merge as-is, fix it before 2.6.13, and you get the same thing, except
a release earlier.  I think this shouldn't be a problem, as after the
floodgates close, you still get to fix things you merged early.  This
came about as a result of feedback received because after it went into
-mm, and it seems to me that this is a legitimate change for 2.6.14.

> And then
> 
> 2a) drop the trick, and avoid changing ptrace call numbers. Old UMLs
> will run fast, but crash with /proc/sysemu (only root-accessible).

We should drop /proc/sysemu, if it's there at all, since it's only for
debugging sysemu, and maintain it as a private patch.  So this doesn't
seem like much of an issue.

				Jeff


-------------------------------------------------------
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-06 16:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-04 15:02 [uml-devel] SYSEMU getting merged - but I'm in doubt Blaisorblade
2005-09-06 16:10 ` Jeff Dike [this message]
2005-09-13 16:51   ` Bodo Stroesser
2005-09-13 18:23     ` Blaisorblade
2005-09-13 20:13       ` Bodo Stroesser
2005-09-14 11:48         ` Bodo Stroesser
2005-09-14 18:01           ` Blaisorblade
2005-09-14 18:19       ` 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=20050906161032.GA6157@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=blaisorblade@yahoo.it \
    --cc=bstroesser@fujitsu-siemens.com \
    --cc=cwright@cs.sunysb.edu \
    --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