linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Cc: Jeff Dike <jdike@addtoit.com>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] UML-patches to prepare UML/s390
Date: Fri, 29 Apr 2005 22:50:32 +0200	[thread overview]
Message-ID: <200504292250.32383.blaisorblade@yahoo.it> (raw)
In-Reply-To: <426E2688.1050203@fujitsu-siemens.com>

On Tuesday 26 April 2005 13:31, Bodo Stroesser wrote:
> Blaisorblade wrote:
> > Other issues follow, which refer to copied code going out-of-date wrt. my
> > local tree (which I have snapshotted some time ago, after I started
> > writing this mail). This is the problem with copying code - and you're
> > starting experiencing it!
> >
> > * important changes for TLS support, clone(), and so on.
>
> I'm going to implement TLS support in UML/s390. I could do this in
> arch/um/sys-s390/syscalls.c/sys_clone() without any need to change generic
> UML code.
> But I guess, for i386 there will be a need for arch-specific code in
> copy_thread(), maybe something like arch_copy_thread().
> If so, s390 TLS support should be inserted using in the same manner.
> Do you already have some code for this, that I could base on?

On my web-site I've uploaded my personal devel-tree snapshot against -rc3. 
Currently I've had to add a "clear_flushed_tls()" to copy_thread(), which 
probably should be wrapped in a arch_copy_thread() (with a macro/inline in 
some header).

As a side note: the TLS code currently does not work yet, so don't rely on it. 
There are also some issues to (later?) consider, which are indicated in the 
patch itself; and there will be something to add to the host SKAS patch, 
because the current implementation would be a bit too slow probably.
-- 
Paolo Giarrusso, aka Blaisorblade
Skype user "PaoloGiarrusso"
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade




-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
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-04-28 20:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06 13:27 [uml-devel] UML-patches to prepare UML/s390 Bodo Stroesser
2005-04-06 20:35 ` [uml-devel] " Jeff Dike
2005-04-06 18:57   ` Bodo Stroesser
2005-04-06 19:17     ` Blaisorblade
2005-04-06 19:26       ` Bodo Stroesser
2005-04-06 19:50         ` Blaisorblade
2005-04-07  9:54           ` Bodo Stroesser
2005-04-06 18:59   ` Bodo Stroesser
2005-04-06 19:16   ` Bastian Blank
2005-04-06 19:28     ` Blaisorblade
2005-04-06 19:33     ` Bodo Stroesser
2005-04-06 20:02       ` Bastian Blank
2005-04-06 20:10         ` Blaisorblade
2005-04-07  9:39         ` Bodo Stroesser
2005-04-07 15:57   ` Bodo Stroesser
2005-04-08  1:22 ` [uml-devel] " Blaisorblade
     [not found]   ` <42562EC4.7040903@fujitsu-siemens.com>
2005-04-17 17:37     ` Blaisorblade
2005-04-18 10:54       ` Bodo Stroesser
2005-04-19 16:45         ` Blaisorblade
2005-04-26 11:31       ` Bodo Stroesser
2005-04-29 20:50         ` Blaisorblade [this message]
2005-04-22  1:32 ` [uml-devel] " Jeff Dike
2005-04-24 14:44   ` Blaisorblade
2005-04-24 16:51     ` Jeff Dike
2005-04-24 18:44       ` 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=200504292250.32383.blaisorblade@yahoo.it \
    --to=blaisorblade@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