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>
Subject: Re: [uml-devel] Re: Needed arch_copy_tls? Not done by dup_task_struct?
Date: Thu, 19 Jan 2006 01:00:26 +0100	[thread overview]
Message-ID: <200601190100.26560.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20060118233846.GA5534@ccure.user-mode-linux.org>

On Thursday 19 January 2006 00:38, Jeff Dike wrote:
> On Wed, Jan 18, 2006 at 08:53:29PM +0100, Blaisorblade wrote:
> > I looked at my patch's comment and noticed that arch_copy_tls, your
> > introduction, shouldn't indeed be needed, because dup_task_struct should
> > do that (it copies the whole task_struct, and it seems that arch_thread
> > is included in that blob rather than pointed too).
> >
> > I'm fairly puzzled at that. Have you any idea on this?
>
> I wondered about that, too, but hadn't bothered looking into it yet.  I'm
> suspicious that we initialize p.thread with INIT_THREAD, which would
> obviously wipe it out.

> > Also, since you have a good test FS (Fedora), can I send you the updated
> > versions I put out / can you test them? My Sarge isn't good any more,
> > likely because glibc was updated by apt-get, and it works well with the
> > LDT fallback.

> I have - they are on my patches page.  I added back the
> user_desc -> modify_ldt_t thing because I don't have a user_desc here.

I'm fixing this by copying the structure definition into sysdep/tls.h header 
files with a different name and using that one in os-Linux/tls.c.

> Other than that (and the O_FORCE succeeded message), it seems to be working
> fine.

> > I've just uploaded 2.6.15-bs1-tls for people to test.

> What I grabbed is what was there this morning.  If you changed anything
> significant, let me know, and I'll pull again.
I'll notify you when needed.
-- 
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! Messenger with Voice: chiama da PC a telefono a tariffe esclusive 
http://it.messenger.yahoo.com



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
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:[~2006-01-19  0:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 19:53 [uml-devel] Needed arch_copy_tls? Not done by dup_task_struct? Blaisorblade
2006-01-18 23:38 ` [uml-devel] " Jeff Dike
2006-01-18 23:39   ` Blaisorblade
2006-01-19  4:38     ` Jeff Dike
2006-01-19  0:00   ` 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=200601190100.26560.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --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