From: Guenter Roeck <linux@roeck-us.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"David S. Miller" <davem@davemloft.net>,
Christoph Hellwig <hch@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
driverdevel <devel@driverdev.osuosl.org>,
Peng Tao <tao.peng@emc.com>, Peng Tao <bergwolf@gmail.com>
Subject: Re: [PATCH] staging: Disable lustre file system for MIPS, SH, and XTENSA
Date: Tue, 10 Sep 2013 09:44:04 -0700 [thread overview]
Message-ID: <20130910164404.GA1690@roeck-us.net> (raw)
In-Reply-To: <CAMuHMdXWaVivv3RL9dyLdeA7p4=XiBLAyhXNEiay3ARoWjM5gw@mail.gmail.com>
On Tue, Sep 10, 2013 at 10:49:05AM +0200, Geert Uytterhoeven wrote:
> On Mon, Sep 9, 2013 at 10:06 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> >> [*] Why does m68k allmodconfig still succeed on kissb???
> >> It does fail for me, as m68k's copy_from_user_page() calls
> >> flush_icache_user_range(), which is not exported.
> >>
> > I don't see a build failure in m68k:allmodconfig either.
> >
> > flush_icache_user_range() is called from copy_to_user_page(), not from
> > copy_from_user_page(). copy_from_user_page() calls flush_cache_page()
> > which calls __flush_cache_030(). The first is inline, the second is
> > assembler, so I would expect it to work. Which doesn't answer
> > the question why it fails for you.
>
> Sorry, I meant copy_to_user_page().
>
> I tried with 2.6.3 from crosstool, and it succeeded, too.
>
Do such old versions of gcc still exist ? Just kidding :)
> Turns out cfs_access_process_vm() is called with write=0 only.
> Gcc 2.6.3 optimizes away the write != 0 branch (which calls copy_to_user_page()
> and thus flush_icache_user_range()), while gcc 4.1.2 doesn't do that.
> Mystery solved.
>
Still bad. Guess it would still fail with 4.6.3 if optimization is turned off.
Guenter
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
next prev parent reply other threads:[~2013-09-10 16:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 1:03 [PATCH] staging: Disable lustre file system for MIPS, SH, and XTENSA Guenter Roeck
2013-09-09 1:59 ` Greg Kroah-Hartman
2013-09-09 2:18 ` Ramkumar Ramachandra
2013-09-09 2:33 ` Greg Kroah-Hartman
2013-09-09 2:38 ` Ramkumar Ramachandra
2013-09-09 2:50 ` Greg Kroah-Hartman
2013-09-09 2:55 ` Ramkumar Ramachandra
2013-09-09 3:21 ` Guenter Roeck
2013-09-09 3:38 ` Ramkumar Ramachandra
2013-09-09 2:24 ` Guenter Roeck
2013-09-09 2:31 ` Greg Kroah-Hartman
2013-09-09 2:31 ` Guenter Roeck
2013-09-09 5:01 ` Heiko Carstens
2013-09-10 17:14 ` Peng Tao
2013-09-11 1:44 ` Christoph Hellwig
2013-09-11 2:25 ` Peng Tao
2013-09-11 2:30 ` Guenter Roeck
2013-09-11 2:51 ` Peng Tao
2013-09-11 16:29 ` Christoph Hellwig
2013-09-11 21:23 ` Dilger, Andreas
2013-09-11 20:48 ` Dilger, Andreas
2013-09-12 8:01 ` Peng Tao
2013-09-09 13:40 ` Christoph Hellwig
2013-09-09 16:39 ` Greg Kroah-Hartman
2013-09-09 17:08 ` Guenter Roeck
2013-09-09 17:22 ` Greg Kroah-Hartman
2013-09-09 19:11 ` Geert Uytterhoeven
2013-09-09 20:06 ` Guenter Roeck
2013-09-10 8:49 ` Geert Uytterhoeven
2013-09-10 16:44 ` Guenter Roeck [this message]
2013-09-10 16:51 ` Geert Uytterhoeven
2013-09-10 17:15 ` Peng Tao
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=20130910164404.GA1690@roeck-us.net \
--to=linux@roeck-us.net \
--cc=bergwolf@gmail.com \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tao.peng@emc.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.