public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Rottinger <steve@pentek.com>
To: linux-rt-users@vger.kernel.org
Cc: tglx@linutronix.de
Subject: Re: PREEMPT_RT + HIGHMEM = segfaults during boot on ppc32
Date: Tue, 07 Jul 2009 14:46:13 -0400	[thread overview]
Message-ID: <4A5397F5.30500@pentek.com> (raw)
In-Reply-To: <4A51F4C1.6060604@pentek.com>

Hi Thomas,

This patch solved my problem.

Thanks!

-Steve

Thomas Gleixner wrote:

> does the patch below help ?
>
> Thanks,
>
>	tglx
> ---
> Subject: powerpc-fixup-pagefault-disable-changes.patch
> From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
> Date: Mon, 06 Jul 2009 17:36:01 +0200
>
> Signed-off-by: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
> ---
> arch/powerpc/include/asm/highmem.h |    3 +++
> 1 file changed, 3 insertions(+)
>
> Index: linux-2.6-tip/arch/powerpc/include/asm/highmem.h
> ===================================================================
> --- linux-2.6-tip.orig/arch/powerpc/include/asm/highmem.h
> +++ linux-2.6-tip/arch/powerpc/include/asm/highmem.h
> @@ -90,6 +90,7 @@ static inline void *kmap_atomic_prot(str
>  	unsigned long vaddr;
>
>  	/* even !CONFIG_PREEMPT needs this, for in_atomic in
> do_page_fault */
> +	preempt_disable();
> 	pagefault_disable();
> 	if (!PageHighMem(page))
> 		return page_address(page);
> @@ -118,6 +119,7 @@ static inline void kunmap_atomic(void *k
>
> 	if (vaddr < __fix_to_virt(FIX_KMAP_END)) {
> 		pagefault_enable();
> +		preempt_enable();
> 		return;
> 	}
>
> @@ -131,6 +133,7 @@ static inline void kunmap_atomic(void *k
>  	local_flush_tlb_page(NULL, vaddr);
>  #endif
> 	pagefault_enable();
> +	preempt_enable();
> }
>
> static inline struct page *kmap_atomic_to_page(void *ptr)

       reply	other threads:[~2009-07-07 18:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4A51F4C1.6060604@pentek.com>
2009-07-07 18:46 ` Steve Rottinger [this message]
2009-07-02 20:18 PREEMPT_RT + HIGHMEM = segfaults during boot on ppc32 Steve Rottinger
2009-07-06 15:43 ` Thomas Gleixner

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=4A5397F5.30500@pentek.com \
    --to=steve@pentek.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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