From: Dmitri Vorobiev <dmitri.vorobiev@movial.fi>
To: Thiemo Seufer <ths@networkno.de>
Cc: Theodore Tso <tytso@MIT.EDU>, Martin Michlmayr <tbm@cyrius.com>,
Ralf Baechle <ralf@linux-mips.org>,
Dmitri Vorobiev <dmitri.vorobiev@gmail.com>,
linux-mips@linux-mips.org, linux-ext4@vger.kernel.org
Subject: Re: ext4dev build failure on mips: "empty_zero_page" undefined
Date: Fri, 06 Jun 2008 09:57:48 +0300 [thread overview]
Message-ID: <4848DFEC.1010800@movial.fi> (raw)
In-Reply-To: <20080605215152.GB15504@networkno.de>
Thiemo Seufer wrote:
> Vorobiev Dmitri wrote:
>> Theodore Tso wrote:
>>> If you really insist I suppose we could have a MIPS specific patch
>>> where we allocate a 4k page and zero it, so we can use it from our
>>> kernel code because you don't want to export and make available the
>>> ZERO_PAGE that gets used by the rest of the kernel, but that seems
>>> awfully silly, and would be a waste of 4k of memory..... Someone from
>>> MIPS land would have to test it, as well, as I dont think any of the
>>> ext4 developers have access to a MIPS platform.
>> Ted, Ralf seems to be unwilling to accept the ZERO_PAGE() export. If you
>> send the MIPS-specific patch, I can do the testing for you as I have a
>> MIPS Malta board at my disposal.
>
> AFAIU the problematic case are systems with R4000/R4400 SC/MC CPUs
> since they use 8 zero pages of different color. Have a look at
> arch/mips/mm/init.c:setup_zero_pages.
OK, thanks for the info. However, I won't be able to tackle into the
issue during this and the next week as I'm having a business trip.
Therefore, if the issue is urgent, I'd be grateful if someone could take
over.
Thanks,
Dmitri
next prev parent reply other threads:[~2008-06-06 6:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 13:06 ext4dev build failure on mips: "empty_zero_page" undefined Martin Michlmayr
2008-05-12 13:54 ` Dmitri Vorobiev
2008-05-12 14:34 ` Theodore Tso
2008-05-12 14:46 ` Dmitri Vorobiev
2008-05-13 4:50 ` Ralf Baechle
2008-05-13 5:12 ` Ralf Baechle
2008-05-15 13:39 ` Theodore Tso
2008-05-28 7:06 ` Martin Michlmayr
2008-06-05 11:11 ` Martin Michlmayr
2008-06-05 11:22 ` Dmitri Vorobiev
2008-06-05 18:38 ` Theodore Tso
2008-06-05 21:34 ` Vorobiev Dmitri
2008-06-05 21:51 ` Thiemo Seufer
2008-06-06 6:57 ` Dmitri Vorobiev [this message]
2008-06-06 13:15 ` Theodore Tso
2008-05-12 14:58 ` Martin Michlmayr
2008-05-12 15:14 ` Dmitri Vorobiev
2008-05-12 17:35 ` Theodore Tso
2008-05-12 19:37 ` Dmitri Vorobiev
2008-05-13 0:55 ` Stephen Rothwell
2008-05-13 1:42 ` Stephen Rothwell
2008-05-13 4:23 ` 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=4848DFEC.1010800@movial.fi \
--to=dmitri.vorobiev@movial.fi \
--cc=dmitri.vorobiev@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=tbm@cyrius.com \
--cc=ths@networkno.de \
--cc=tytso@MIT.EDU \
/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;
as well as URLs for NNTP newsgroup(s).