linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	Antoine Martin <antoine@nagafix.co.uk>
Subject: [uml-devel] TLS support - status - need for re-testing
Date: Thu, 23 Mar 2006 03:17:45 +0100	[thread overview]
Message-ID: <200603230317.48384.blaisorblade@yahoo.it> (raw)

I've integrated "linux-unistd" from Jeff series, while leaving out 
"user-desc" (I've solved the problem another way, which should work on both 
host header set - we give our own definition for userspace files, and use our 
one for kernelspace, but give the resulting type the name of "user_desc_t").
Jeff, I've looked at all other patches _names_ and they're patches which I 
already have, so I shouldn't have lost any other changes.

Plus, I've just done a couple of other cleanups of the TLS code, removing dead 
code which was there for experiments; I've implemented 2.4 host detection (I 
hope I've not forgot to check the host_supports_tls variable anywhere), and 
I'm ripping out global-ldt-sem which I longly hated (and which isn't easy to 
avoid).

I've ripped it out by comparing header dependencies to i386; the result is 
that our additional dependency is from processor.h and ptrace.h on ldt.h, but 
they only depend on the user_desc declaration and not on the uml_ldt_t 
declaration (which is the one using the semaphore).

So I split the user_desc part away in a new header file, and this fixed the 
problem.

However, I tested seriously the new code and it doesn't work with apache2 
mpm-worker nor with simpler tests.... I hadn't run such tests recently, and I 
now see that the code does assumptions which are wrong on x86_64 hosts.

Has anyone got success or failure with TLS code on 32-bit machines on 64-bit 
hosts?

More important: has anyone tested that?
-- 
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 xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&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

             reply	other threads:[~2006-03-23  2:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23  2:17 Blaisorblade [this message]
2006-03-23 11:29 ` [uml-devel] Re: TLS support - status - need for re-testing Antoine Martin
2006-03-23 21:14 ` Jeff Dike
2006-03-23 23:44   ` Blaisorblade
2006-03-24  1:51     ` Jeff Dike
2006-03-24 10:39       ` Antoine Martin
2006-03-24 11:44         ` Blaisorblade
2006-03-24 11:43       ` Blaisorblade
2006-03-24  4:17     ` Jeff Dike
2006-03-24 11:43       ` Blaisorblade
2006-03-24 17:32         ` Jeff Dike
2006-03-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=200603230317.48384.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=antoine@nagafix.co.uk \
    --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