linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>, Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [uml-devel] Re: UML/2.6.14-rc3 doesn't work fixes
Date: Sun, 9 Oct 2005 21:16:41 +0200	[thread overview]
Message-ID: <200510092116.41711.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20051004172446.GL7992@ftp.linux.org.uk>

On Tuesday 04 October 2005 19:24, Al Viro wrote:
> 	Taking clone.c to sys-*, making it a normal kernel object, trimming
> stub.h
This deserves a bit more attention.

In fact, it is a possible fix to a misassembling problem - the current code 
loads registers in one asm() statement and expects them to be left unaltered 
in subsequent ones, which sometimes breaks.

But currently it breaks things, as this clone.c must be totally self-contained 
(it doesn't run in the kernel address space - think of vsyscall.S).
Btw, do you ever try booting UML? Seems not always, at least...

And "static int errno" isn't enough - it must be placed in the data section of 
the stub, but I don't want to address this for 2.6.14 (even because we are 
creating a new address space and I don't want to deal with stack lifecycles 
right now).

In fact, I've put together another patch for this, partly copying unistd.h 
macros. For your patch, we must resolve the errno problem first.

Also, making clone.c a kernel object is not conceptually right, because it is 
actually host-kernel specific (yes, we haven't ports to other host kernels, 
for now).
-- 
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade


	

	
		
___________________________________ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
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-10-09 19:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-02 10:13 [uml-devel] UML/2.6.14-rc3 doesn't work fixes Blaisorblade
2005-10-02 11:38 ` [uml-devel] " Al Viro
2005-10-02 11:50   ` Blaisorblade
2005-10-02 17:32     ` Al Viro
2005-10-02 17:45       ` Blaisorblade
2005-10-02 15:51 ` Jeff Dike
2005-10-02 16:55   ` Al Viro
2005-10-02 18:01   ` Blaisorblade
2005-10-02 18:37     ` Al Viro
2005-10-02 20:54       ` Al Viro
2005-10-03 18:30         ` Blaisorblade
2005-10-03 23:38           ` Al Viro
2005-10-04 10:26             ` Blaisorblade
2005-10-04 11:09               ` Al Viro
2005-10-04 11:19                 ` Blaisorblade
2005-10-04 11:55                   ` Al Viro
2005-10-04 12:09                     ` Blaisorblade
2005-10-04 17:09           ` Al Viro
2005-10-04 17:14             ` Al Viro
2005-10-04 17:18               ` Al Viro
2005-10-04 17:24                 ` Al Viro
2005-10-04 17:28                   ` Al Viro
2005-10-09 19:16                   ` Blaisorblade [this message]
2005-10-03 18:56       ` 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=200510092116.41711.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=viro@zeniv.linux.org.uk \
    /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