From: Blaisorblade <blaisorblade@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Needed arch_copy_tls? Not done by dup_task_struct?
Date: Wed, 18 Jan 2006 20:53:29 +0100 [thread overview]
Message-ID: <200601182053.31322.blaisorblade@yahoo.it> (raw)
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?
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've just uploaded 2.6.15-bs1-tls for people to test.
--
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: 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
next reply other threads:[~2006-01-18 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 19:53 Blaisorblade [this message]
2006-01-18 23:38 ` [uml-devel] Re: Needed arch_copy_tls? Not done by dup_task_struct? Jeff Dike
2006-01-18 23:39 ` Blaisorblade
2006-01-19 4:38 ` Jeff Dike
2006-01-19 0:00 ` 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=200601182053.31322.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