linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Roland Dreier <rolandd@cisco.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] PPC: Don't sleep in flush_dcache_icache_page()
Date: Thu, 18 Aug 2005 14:56:42 -0300	[thread overview]
Message-ID: <20050818175642.GA7523@dmt.cnet> (raw)
In-Reply-To: <521x4tha7i.fsf@cisco.com>


Hi Roland,

On Tue, Aug 16, 2005 at 01:56:49PM -0700, Roland Dreier wrote:
> flush_dcache_icache_page() will be called on an instruction page
> fault.  We can't sleep in the fault handler, so use kmap_atomic()
> instead of just kmap() for the Book-E case.
> 
> Signed-off-by: Roland Dreier <rolandd@cisco.com>

Why do you need to disable interrupts during the kmap_atomic/flush_dcache_icache
operation ? 

I fail to see how an interrupt could have any reference to the data
being dealt with here (the user page).

> diff --git a/arch/ppc/mm/init.c b/arch/ppc/mm/init.c
> --- a/arch/ppc/mm/init.c
> +++ b/arch/ppc/mm/init.c
> @@ -560,8 +560,16 @@ void flush_dcache_page(struct page *page
>  void flush_dcache_icache_page(struct page *page)
>  {
>  #ifdef CONFIG_BOOKE
> -	__flush_dcache_icache(kmap(page));
> -	kunmap(page);
> +	unsigned long flags;
> +	void *start;
> +
> +	local_irq_save(flags);
> +
> +	start = kmap_atomic(page, KM_PPC_SYNC_PAGE);
> +	__flush_dcache_icache(start);
> +	kunmap_atomic(start, KM_PPC_SYNC_PAGE);
> +
> +	local_irq_restore(flags);
>  #elif CONFIG_8xx
>  	/* On 8xx there is no need to kmap since highmem is not supported */
>  	__flush_dcache_icache(page_address(page)); 

  reply	other threads:[~2005-08-18 18:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 20:56 [PATCH] PPC: Don't sleep in flush_dcache_icache_page() Roland Dreier
2005-08-18 17:56 ` Marcelo Tosatti [this message]
2005-08-18 18:08   ` Matt Porter

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=20050818175642.GA7523@dmt.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=rolandd@cisco.com \
    /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;
as well as URLs for NNTP newsgroup(s).