From: Paul Mundt <lethal@linux-sh.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: rmk@arm.linux.org.uk, linux-arch@vger.kernel.org
Subject: Re: Changing update_mmu_cache()
Date: Mon, 28 Feb 2005 11:18:43 +0200 [thread overview]
Message-ID: <20050228091843.GA5709@linux-sh.org> (raw)
In-Reply-To: <20050227201208.7e0a5217.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 1789 bytes --]
On Sun, Feb 27, 2005 at 08:12:08PM -0800, David S. Miller wrote:
> What are you patching against? In the patch I sent, which are you
> replying to, I made flush_icache_user_range() in this file be:
>
> void flush_icache_user_range(struct vm_area_struct *vma,
> struct page *page, unsigned long addr, int len)
> {
> __flush_cache_page(vma, addr,
> PHYSADDR(page_address(page)) >> PAGE_SHIFT);
> }
>
Yes, you're right, wrong tree, sorry for the confusion. Here are the
fixes against your patch:
===== arch/sh/mm/cache-sh4.c 1.10 vs edited =====
--- 1.10/arch/sh/mm/cache-sh4.c 2005-02-28 11:14:14 +02:00
+++ edited/arch/sh/mm/cache-sh4.c 2005-02-28 11:15:27 +02:00
@@ -357,7 +357,6 @@
void flush_icache_user_range(struct vm_area_struct *vma,
struct page *page, unsigned long addr, int len)
{
- __flush_cache_page(vma, addr,
- PHYSADDR(page_address(page)) >> PAGE_SHIFT);
+ flush_cache_page(vma, addr, page_to_pfn(page));
}
===== arch/sh64/mm/cache.c 1.2 vs edited =====
--- 1.2/arch/sh64/mm/cache.c 2005-02-28 11:14:14 +02:00
+++ edited/arch/sh64/mm/cache.c 2005-02-28 11:15:01 +02:00
@@ -573,11 +573,6 @@
}
}
-static inline void sh64_dcache_purge_virt_page(struct mm_struct *mm, unsigned long eaddr, unsigned long pfn)
-{
- sh64_dcache_purge_phy_page(pfn << PAGE_SHIFT);
-}
-
static void sh64_dcache_purge_user_page(struct mm_struct *mm, unsigned long eaddr)
{
pgd_t *pgd;
@@ -895,7 +890,7 @@
Note(1), this is called with mm->page_table_lock held.
*/
- sh64_dcache_purge_virt_page(vma->vm_mm, eaddr, pfn);
+ sh64_dcache_purge_phy_page(pfn << PAGE_SHIFT);
if (vma->vm_flags & VM_EXEC) {
sh64_icache_inv_user_page(vma, eaddr);
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-02-28 9:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 4:53 Changing update_mmu_cache() Benjamin Herrenschmidt
2005-02-22 5:43 ` David S. Miller
2005-02-22 9:07 ` Russell King
2005-02-22 18:08 ` David S. Miller
2005-02-25 20:15 ` Russell King
2005-02-25 21:43 ` Andrew Morton
2005-02-25 21:46 ` William Lee Irwin III
2005-02-25 22:48 ` Russell King
2005-02-25 22:59 ` William Lee Irwin III
2005-02-25 23:07 ` Andrew Morton
2005-02-26 1:09 ` David S. Miller
2005-02-27 18:55 ` Paul Mundt
2005-02-28 4:12 ` David S. Miller
2005-02-28 9:18 ` Paul Mundt [this message]
2005-03-06 5:15 ` David S. Miller
2005-02-27 19:27 ` Russell King
2005-02-26 1:10 ` Benjamin Herrenschmidt
2005-02-22 20:51 ` Benjamin Herrenschmidt
2005-02-23 5:35 ` Changing update_mmu_cache() or set_pte() ? Benjamin Herrenschmidt
2005-02-23 5:47 ` Benjamin Herrenschmidt
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=20050228091843.GA5709@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=davem@davemloft.net \
--cc=linux-arch@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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