All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: disable preemption in apply_to_pte_range
Date: Thu, 12 Feb 2009 16:35:30 -0800	[thread overview]
Message-ID: <4994C052.9060907@goop.org> (raw)
In-Reply-To: <4994BCF0.30005@goop.org>

Jeremy Fitzhardinge wrote:
> commit 79d9c90453a7bc9e7613ae889a97ff6b44ab8380

Scratch that.  This instead.
    J

    mm: disable preemption in apply_to_pte_range
    
    Lazy mmu mode needs preemption disabled, so if we're apply to
    init_mm (which doesn't require any pte locks), then explicitly
    disable preemption.  (Do it unconditionally after checking we've
    successfully done the allocation to simplify the error handling.)
    
    Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>

diff --git a/mm/memory.c b/mm/memory.c
index baa999e..b80cc31 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -1718,6 +1718,7 @@ static int apply_to_pte_range(struct mm_struct *mm, pmd_t *pmd,
 
 	BUG_ON(pmd_huge(*pmd));
 
+	preempt_disable();
 	arch_enter_lazy_mmu_mode();
 
 	token = pmd_pgtable(*pmd);
@@ -1729,6 +1730,7 @@ static int apply_to_pte_range(struct mm_struct *mm, pmd_t *pmd,
 	} while (pte++, addr += PAGE_SIZE, addr != end);
 
 	arch_leave_lazy_mmu_mode();
+	preempt_enable();
 
 	if (mm != &init_mm)
 		pte_unmap_unlock(pte-1, ptl);



  reply	other threads:[~2009-02-13  0:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13  0:21 [PATCH] mm: disable preemption in apply_to_pte_range Jeremy Fitzhardinge
2009-02-13  0:35 ` Jeremy Fitzhardinge [this message]
2009-02-13  0:55   ` Andrew Morton
2009-02-13  0:55     ` Andrew Morton
2009-02-13  1:39     ` Jeremy Fitzhardinge
2009-02-13  1:39       ` Jeremy Fitzhardinge
2009-02-13 11:48       ` Peter Zijlstra
2009-02-13 11:48         ` Peter Zijlstra
2009-02-13 13:30         ` Nick Piggin
2009-02-13 13:30           ` Nick Piggin
2009-02-13 14:16           ` Peter Zijlstra
2009-02-13 14:16             ` Peter Zijlstra
2009-02-13 14:30             ` Nick Piggin
2009-02-13 14:30               ` Nick Piggin
2009-02-13 14:38               ` Peter Zijlstra
2009-02-13 14:38                 ` Peter Zijlstra
2009-02-13 17:41                 ` Jeremy Fitzhardinge
2009-02-13 17:41                   ` Jeremy Fitzhardinge
2009-02-14  9:46                   ` Peter Zijlstra
2009-02-14  9:46                     ` Peter Zijlstra
2009-02-13 17:24         ` Jeremy Fitzhardinge
2009-02-13 17:24           ` Jeremy Fitzhardinge
2009-02-14  9:56           ` Peter Zijlstra
2009-02-14  9:56             ` Peter Zijlstra

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=4994C052.9060907@goop.org \
    --to=jeremy@goop.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.