All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: Franck <vagabon.xyz@gmail.com>, linux-mips@linux-mips.org
Subject: Re: [RFC] Add 4KSx support (try 2)
Date: Mon, 31 Oct 2005 11:15:19 +0000	[thread overview]
Message-ID: <20051031111519.GA13281@linux-mips.org> (raw)
In-Reply-To: <4365DF22.8060004@mips.com>

On Mon, Oct 31, 2005 at 10:08:50AM +0100, Kevin D. Kissell wrote:

> There are places, for example arch/mips/mm/cache.c, but
> also some of the other makefiles, where you're using your
> new config flags to drive things where the standard
> CONFIG_CPU_MIPS32 (which I guess has now fragmented into
> CONFIG_CPU_MIPS32_R1 and CONFIG_CPU_MIPS32_R2, which would
> apply to the Sc and Sd respectively) would do the right thing
> while creating fewer source file mods.

CONFIG_CPU_MIPS32 is a short cut; it's set if any of CONFIG_CPU_MIPS32_R1
or CONFIG_CPU_MIPS32_R2 is set.  Equivalent for MIPS64.  Another short
set of short cuts is CONFIG_CPU_MIPSR1 which is set if any of
CONFIG_CPU_MIPS32_R1 or CONFIG_CPU_MIPS64_R1 is set and again the
equivalent thing for CONFIG_CPU_MIPSR2 exists.

> Have you thought about what the ACX state would mean for
> kernel debuggers in general and kgdb in particular?

The real issue I have with the patch is that ACX is extending the state
that would need to be saved and restored in signal handlers and I have to
solve the question where to keep that information without breaking
compatibility - that's pretty much the same exercise which we had just
recently with adding DSP support.  I need to look into that Franck; until
this patch is on hold.  It however looks correct otherwise.

  Ralf

  reply	other threads:[~2005-10-31 11:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31  8:34 [RFC] Add 4KSx support (try 2) Franck
2005-10-31  9:08 ` Kevin D. Kissell
2005-10-31 11:15   ` Ralf Baechle [this message]
2005-10-31 16:21     ` Franck
2005-10-31 16:01   ` Franck
2005-10-31 17:45     ` Kevin D. Kissell
2005-11-01  8:34       ` Franck

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=20051031111519.GA13281@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=kevink@mips.com \
    --cc=linux-mips@linux-mips.org \
    --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 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.