All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gleb O. Raiko" <raiko@niisi.msk.ru>
To: Keith Owens <kaos@ocs.com.au>
Cc: "'linux-mips@oss.sgi.com'" <linux-mips@oss.sgi.com>
Subject: Re: DBE table ordering
Date: Thu, 18 Apr 2002 13:37:14 +0400	[thread overview]
Message-ID: <3CBE93CA.EB27DB1A@niisi.msk.ru> (raw)
In-Reply-To: 314.1019112700@ocs3.intra.ocs.com.au

Keith,

Keith Owens wrote:
> 
> This is a more general problem than mips dbe, other kernel tables and
> other architectures will have the same problem.  I will do a general
> patch against 2.5.8 to sort these tables at init time, and backport the
> general fix to 2.4.19 later.  In the meantime your patch will bypass
> the problem for mips dbe.

Consider it as a feature. It was known from the time Ralf designed it. 

If you really hate this behaviour and want to change it, I guess just
linear serach is OK. Or just introduce set of get/put_dbe{b,w,l}
routines instead of macros and expect just one fault address (well, 6
addresses, if you care). I think, it's better than rearranging the table
on startup (your proposal) and searching in several dbe tables (was
introduced last year).

Another table (in fact, I know only the unaligned access table in
arch/mips*/unaligned.c) is immune, because call from an __init routine
from user space is somewhat tricky and, anyway, isn't allowed.

If you know other tables, I think it's better to find a solution on
individual basis. No needs for a common solution here. 

Regards,
Gleb.

  reply	other threads:[~2002-04-18  9:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17 22:21 DBE table ordering Mark Huang
2002-04-18  3:55 ` Keith Owens
2002-04-18  6:39   ` Mark Huang
2002-04-18  6:39     ` Mark Huang
2002-04-18  6:51     ` Keith Owens
2002-04-18  6:51       ` Keith Owens
2002-04-18  9:37       ` Gleb O. Raiko [this message]
2002-04-18  9:49         ` Keith Owens
2002-04-18 12:03           ` Gleb O. Raiko
2002-04-18 17:59             ` Maciej W. Rozycki
2002-04-19  8:28               ` Gleb O. Raiko
2002-04-19 12:19                 ` Maciej W. Rozycki

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=3CBE93CA.EB27DB1A@niisi.msk.ru \
    --to=raiko@niisi.msk.ru \
    --cc=kaos@ocs.com.au \
    --cc=linux-mips@oss.sgi.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.