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
Subject: Re: [uml-devel] Fwd: Re: Why uml-add-tls-support-debug-check-never-works is needed
Date: Tue, 28 Mar 2006 00:56:07 +0200	[thread overview]
Message-ID: <200603280056.09452.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20060326204026.GB4549@ccure.user-mode-linux.org>

[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]

On Sunday 26 March 2006 22:40, Jeff Dike wrote:	
> And, BTW, you should probably send the TLS stuff in this week if you
> want it to go into 2.6.17 easily.

Ok, I've just finished everything (including proper detection of ) and feel 
satisfied of the code. However, look at the attached patch - it's a cosmetic 
bug which I found while testing TLS, and I'd like you to review it.

Meanwhile, I'm releasing 2.6.16-bb1 with the TLS stuff and this patch 
included, plus various other little stuff.

I hope this week I can send TLS in mainline, however we should be able to get 
it even if it's a few days past the deadline.

My current problem is that out of a whole week, I can only hack on Wednesday 
afternoon, or on the weekend (read sunday afternoon) if I can do that, or 
after dinner. I'd have a lot of time on early morning, but you can understand 
it goes easily wasted because I must sleep.
-- 
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: uml-fix-mm-usage-in-cpu_idle --]
[-- Type: text/x-diff, Size: 1020 bytes --]

uml idle thread needn't take access to init_mm

From: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>

Comparing this code which is the actual body of the arch-independent cpu_idle(),
it is clear that it's unnecessary to set ->mm and ->active_mm; beyond that, a
kernel thread is not supposed to have ->mm != NULL, only active_mm.

This showed up because I used the assumption (which is IMHO valid) that kernel
thread have their ->mm == NULL, and it failed for this thread.

Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
Index: linux-2.6.16/arch/um/kernel/process_kern.c
===================================================================
--- linux-2.6.16.orig/arch/um/kernel/process_kern.c
+++ linux-2.6.16/arch/um/kernel/process_kern.c
@@ -201,10 +201,6 @@ void default_idle(void)
 {
 	CHOOSE_MODE(uml_idle_timer(), (void) 0);
 
-	atomic_inc(&init_mm.mm_count);
-	current->mm = &init_mm;
-	current->active_mm = &init_mm;
-
 	while(1){
 		/* endless idle loop with no priority at all */
 

      reply	other threads:[~2006-03-27 22:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-26 18:03 [uml-devel] Fwd: Re: Why uml-add-tls-support-debug-check-never-works is needed (was: Re: Fwd: Proposed additions to the ptrace(2) manpage, take 2) Blaisorblade
2006-03-26 20:38 ` Jeff Dike
2006-03-26 20:40 ` Jeff Dike
2006-03-27 22:56   ` 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=200603280056.09452.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