From: Blaisorblade <blaisorblade@yahoo.it>
To: Antoine Martin <antoine@nagafix.co.uk>
Cc: Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: TLS support - status - need for re-testing
Date: Fri, 24 Mar 2006 12:44:40 +0100 [thread overview]
Message-ID: <200603241244.40735.blaisorblade@yahoo.it> (raw)
In-Reply-To: <1143196799.2868.1.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1779 bytes --]
On Friday 24 March 2006 11:39, Antoine Martin wrote:
> On Thu, 2006-03-23 at 20:51 -0500, Jeff Dike wrote:
> > On Fri, Mar 24, 2006 at 12:44:05AM +0100, Blaisorblade wrote:
> > > Yes, that is true, but meanwhile give a testing to them, especially
> > > regressio test the new patches. I can't merge new patches in until I'm
> > > sure they don't cause regressions.
> >
> > OK, I give it a thumbs-up on a first boot - it's running my FC5
> > filesystem without any trouble. I'll keep playing with it and let you
> > know of any trouble.
>
> I haven't been able to run FC4/FC5 x86 filesystems with any of the
> patches floating around. (on amd64 host)
I can inform you it's not FC4/FC5 but it's the amd64 host.
I missed this because I hadn't time for proper tests before, however:
add on top of 2.6.15-bb6 the attached patch. (It should more or less work
against any other tls patchset, but I tested it like this).
Don't compile the resulting kernel for x86, and don't run the UML you get on
x86 host!
As you can see (it touches include/asm-i386 only), this patch is an quick hack
made for testing, but I know how to fix it, and I'm going to code it.
> > Attached is a tarball of the patches merged after the patches I have
> > planned for 2.6.17. Nothing major, just some fuzz, some Makefile
> > rejections, and rejections from some whitespace cleanup in
> > kernel/skas/process_kern.c.
> I couldn't figure out in which order I need to apply these (no series
> file) and I've ran out of time.
Guess it's -bb6 series file (or I won't be able to apply them).
> Antoine
--
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
[-- Attachment #2: workaround-x86_64-host-problem --]
[-- Type: text/x-diff, Size: 521 bytes --]
Only for testing on x86_64 hosts.
Index: linux-2.6.15/include/asm-i386/segment.h
===================================================================
--- linux-2.6.15.orig/include/asm-i386/segment.h
+++ linux-2.6.15/include/asm-i386/segment.h
@@ -46,7 +46,7 @@
* 31 - TSS for double fault handler
*/
#define GDT_ENTRY_TLS_ENTRIES 3
-#define GDT_ENTRY_TLS_MIN 6
+#define GDT_ENTRY_TLS_MIN 12
#define GDT_ENTRY_TLS_MAX (GDT_ENTRY_TLS_MIN + GDT_ENTRY_TLS_ENTRIES - 1)
#define TLS_SIZE (GDT_ENTRY_TLS_ENTRIES * 8)
next prev parent reply other threads:[~2006-03-24 11:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 2:17 [uml-devel] TLS support - status - need for re-testing Blaisorblade
2006-03-23 11:29 ` [uml-devel] " 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 [this message]
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=200603241244.40735.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