From: Ralf Baechle <ralf@linux-mips.org>
To: naveen yadav <yad.naveen@gmail.com>
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: flush_kernel_vmap_range() invalidate_kernel_vmap_range() API not exists for MIPS
Date: Fri, 25 Mar 2011 18:27:09 +0100 [thread overview]
Message-ID: <20110325172709.GC8483@linux-mips.org> (raw)
In-Reply-To: <AANLkTimkh2QLvupu+62NGrKfqRb_gC7KLCAKkEoS9N9N@mail.gmail.com>
On Fri, Mar 25, 2011 at 02:38:13PM +0530, naveen yadav wrote:
> We are working on 2.6.35.9 linux kernel on MIPS 34kce core and our
> cache is VIVT having cache aliasing .
No, they're VIPT unless you successfully modified your 34K core to
change it from a less than perfect cache design to the most lunatic
cache policy known to man kind ...
> When I check the implementation on ARM I can check the implemenation
> exists , but there is not similar implementation exists on MIPS.
> These API's are used by XFS module:
>
> static inline void flush_kernel_vmap_range(void *vaddr, int size)
> static inline void invalidate_kernel_vmap_range(void *vaddr, int size)
> static inline void flush_kernel_dcache_page(struct page *page)
A known problem for (too ...) long. I'll finally take care of it.
Ralf
next prev parent reply other threads:[~2011-03-25 17:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 9:08 flush_kernel_vmap_range() invalidate_kernel_vmap_range() API not exists for MIPS naveen yadav
2011-03-25 17:27 ` Ralf Baechle [this message]
2011-03-29 5:54 ` naveen yadav
2011-05-19 4:35 ` naveen yadav
2011-06-15 6:28 ` naveen yadav
2011-06-16 18:02 ` Christoph Hellwig
2011-06-17 15:20 ` Ralf Baechle
2011-06-18 10:51 ` naveen yadav
2011-06-18 13:06 ` Sergei Shtylyov
2011-06-20 9:56 ` Ralf Baechle
2011-06-24 5:06 ` naveen yadav
2011-06-24 7:09 ` Ralf Baechle
2011-06-17 0:05 ` Ralf Baechle
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=20110325172709.GC8483@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=yad.naveen@gmail.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 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.