From: Ralf Baechle <ralf@linux-mips.org>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-mips@linux-mips.org, Ravi.Pratap@hillcrestlabs.com
Subject: Re: flush_anon_page for MIPS
Date: Fri, 23 Mar 2007 15:36:21 +0000 [thread overview]
Message-ID: <20070323153621.GB19477@linux-mips.org> (raw)
In-Reply-To: <cda58cb80703230801v5ce4baacr9b40119ff3342ac8@mail.gmail.com>
On Fri, Mar 23, 2007 at 04:01:04PM +0100, Franck Bui-Huu wrote:
> Date: Fri, 23 Mar 2007 16:01:04 +0100
> From: "Franck Bui-Huu" <vagabon.xyz@gmail.com>
> To: "Ralf Baechle" <ralf@linux-mips.org>
> Subject: Re: flush_anon_page for MIPS
> Cc: "Miklos Szeredi" <miklos@szeredi.hu>, linux-mips@linux-mips.org,
> Ravi.Pratap@hillcrestlabs.com
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 3/23/07, Ralf Baechle <ralf@linux-mips.org> wrote:
> >+#define ARCH_HAS_FLUSH_ANON_PAGE
> >+static inline void flush_anon_page(struct vm_area_struct *vma,
> >+ struct page *page, unsigned long vmaddr)
> >+{
> >+ extern void __flush_anon_page(struct vm_area_struct *vma,
> >+ struct page *, unsigned long);
> >+ if (PageAnon(page))
> >+ __flush_anon_page(vma, page, vmaddr);
> >+}
> >+
>
> Shouldn't you add a test against cpu_has_dc_aliases here and thus
> avoid an useless call to __flush_anon_page() ?
Yes, that's one of the things left to do. On alias-free processors where
cpu_has_dc_aliases was defined to 0 in cpu-feature-overrides.h this will
result in the entire function call to be eleminated by the compiler. Of
course that will still leave the unused body of __flush_anon_page around,
how sad ;)
Ralf
next prev parent reply other threads:[~2007-03-23 15:36 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 22:28 flush_anon_page for MIPS Miklos Szeredi
2007-03-23 14:19 ` Ralf Baechle
2007-03-23 14:19 ` Ralf Baechle
2007-03-23 14:47 ` Franck Bui-Huu
2007-03-23 15:20 ` Ralf Baechle
2007-03-23 21:00 ` Franck Bui-Huu
2007-03-23 21:20 ` Ralf Baechle
2007-03-23 14:51 ` Ravi Pratap
2007-03-23 14:51 ` Ravi Pratap
2007-03-23 15:41 ` Atsushi Nemoto
2007-03-23 15:47 ` Ravi Pratap
2007-03-23 15:47 ` Ravi Pratap
2007-03-23 15:50 ` Atsushi Nemoto
2007-03-26 13:31 ` Atsushi Nemoto
2007-03-26 13:36 ` Ravi Pratap
2007-03-26 13:36 ` Ravi Pratap
2007-03-26 14:33 ` Ralf Baechle
2007-03-23 15:56 ` Ralf Baechle
2007-03-23 15:59 ` Ravi Pratap
2007-03-23 15:59 ` Ravi Pratap
2007-03-23 16:11 ` Maxime Bizon
2007-03-23 16:12 ` Franck Bui-Huu
2007-03-23 16:17 ` Ravi Pratap
2007-03-23 16:17 ` Ravi Pratap
2007-03-23 19:06 ` Ralf Baechle
2007-03-23 22:17 ` Ravi Pratap
2007-03-23 22:17 ` Ravi Pratap
2007-03-23 23:36 ` Ralf Baechle
2007-03-24 0:03 ` David Daney
2007-03-26 13:33 ` Ravi Pratap
2007-03-26 13:33 ` Ravi Pratap
2007-03-26 14:05 ` Ralf Baechle
2007-03-26 22:38 ` Ravi Pratap
2007-03-26 22:38 ` Ravi Pratap
2007-03-26 23:24 ` Ravi Pratap
2007-03-26 23:24 ` Ravi Pratap
2007-03-27 3:17 ` Atsushi Nemoto
2007-03-27 14:51 ` Ravi Pratap
2007-03-27 14:51 ` Ravi Pratap
2007-03-28 14:25 ` Ravi Pratap
2007-03-28 14:25 ` Ravi Pratap
2007-03-28 17:10 ` David Daney
2007-03-28 18:17 ` Ravi Pratap
2007-03-28 18:17 ` Ravi Pratap
2007-03-28 20:34 ` Ralf Baechle
2007-03-28 20:38 ` David Daney
2007-03-23 15:01 ` Franck Bui-Huu
2007-03-23 15:36 ` Ralf Baechle [this message]
2007-03-23 20:52 ` Franck Bui-Huu
2007-03-23 16:22 ` Miklos Szeredi
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=20070323153621.GB19477@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Ravi.Pratap@hillcrestlabs.com \
--cc=linux-mips@linux-mips.org \
--cc=miklos@szeredi.hu \
--cc=vagabon.xyz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox