From: "David S. Miller" <davem@davemloft.net>
To: Paul Mundt <lethal@linux-sh.org>
Cc: rmk@arm.linux.org.uk, linux-arch@vger.kernel.org
Subject: Re: Changing update_mmu_cache()
Date: Sun, 27 Feb 2005 20:12:08 -0800 [thread overview]
Message-ID: <20050227201208.7e0a5217.davem@davemloft.net> (raw)
In-Reply-To: <20050227185537.GB32383@linux-sh.org>
On Sun, 27 Feb 2005 20:55:37 +0200
Paul Mundt <lethal@linux-sh.org> wrote:
> Looks good, thanks. flush_icache_user_range() needed one minor change:
...
> 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)));
> + flush_cache_page(vma, addr, page_to_pfn(page));
> }
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);
}
> > I'll push this off to Linus when 2.6.12 opens up. If folks could
> > build test this against current 2.6.x and report any failures that
> > need fixing, I would appreciate that.
> >
> You missed fs/binfmt_elf.c, this gets it working..
Again, what the heck are you patching against?
It's definitely not the patch I posted which you are
replying to. The tree would not have built for me
on 4 platforms with this error :-)
> On another note, for sh64 we don't need to actually keep
> sh64_dcache_purge_virt_page() around for anything after this change..
> flush_cache_page() was the only user of it anyways, so it makes more
> sense to just have it call sh64_dcache_purge_phy_page() directly.
>
> Here's a patch for arch/sh64/mm/cache.c that you can use in-place of the
> one you have now, builds and boots.
Again, what are you patching against? None of your patches are against
my patch at all.
next prev parent reply other threads:[~2005-02-28 4:12 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 [this message]
2005-02-28 9:18 ` Paul Mundt
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=20050227201208.7e0a5217.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=lethal@linux-sh.org \
--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