All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Thiemo Seufer <ths@networkno.de>
Cc: Vorobiev Dmitri <dmitri.vorobiev@movial.fi>,
	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, 6 Jun 2008 09:15:47 -0400	[thread overview]
Message-ID: <20080606131547.GB9033@mit.edu> (raw)
In-Reply-To: <20080605215152.GB15504@networkno.de>

On Thu, Jun 05, 2008 at 10:51:52PM +0100, Thiemo Seufer wrote:
> > 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.

Ralf sent me a private note saying he would take care of this, but
that he had been very busy with real-world life items.

> 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.

Right.  So we're not actually going to ever write to the page, but we
are going to add the page to a bio and submit for writing.  I assume
that's not going to cause VECI/VCED exceptions, right?  If the act of
DMA'ing, or worse yet, for older devices/drivers which have to use PIO
to write out a block device is going to cause "thousand and thousands
of exceptions", it sounds like MIPS CPU designers need to be slapped
silly....

					- Ted

  parent reply	other threads:[~2008-06-06 13:16 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
2008-06-06 13:15                     ` Theodore Tso [this message]
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=20080606131547.GB9033@mit.edu \
    --to=tytso@mit.edu \
    --cc=dmitri.vorobiev@gmail.com \
    --cc=dmitri.vorobiev@movial.fi \
    --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 \
    /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.