From: Franck <vagabon.xyz@gmail.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [RFC] Add 4KSx support (try 2)
Date: Mon, 31 Oct 2005 17:01:42 +0100 [thread overview]
Message-ID: <cda58cb80510310801v2d60f60bh@mail.gmail.com> (raw)
In-Reply-To: <4365DF22.8060004@mips.com>
Thanks Kevin for responding !
2005/10/31, Kevin D. Kissell <kevink@mips.com>:
> I'm not set up to actually apply and test the patch,
> but for whatever it's worth, the functionality in the patch
> appears to be superficially correct, and more-or-less
> what I would have done. That having been said, I think
> you're creating more changes than are really required.
>
> Having seperate target call-outs for the Sc/Sd in the
> arch/mips/kernel/Makefile just to avoid having r4k_fpu.o
> linked it creates cruft for a savings of 400-odd bytes
> of kernel image, and I'd either have not bothered or have
> figured out a more generic way to strip out FP support
> for FP-less cores.
>
> 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.
>
That's correct but CONFIG_CPU_MIPS32_Rx seems to be a fallback case.
Don't other cpu use their own flags whereas they could just use
CONFIG_CPU_MIPS32_Rx flag instead ?
> Have you thought about what the ACX state would mean for
> kernel debuggers in general and kgdb in particular?
>
no, I didn't. I took a look at arch/mips/kernel/gdb-low.S and it seems
to be required....
Thanks
--
Franck
next prev parent reply other threads:[~2005-10-31 16:01 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
2005-10-31 16:21 ` Franck
2005-10-31 16:01 ` Franck [this message]
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=cda58cb80510310801v2d60f60bh@mail.gmail.com \
--to=vagabon.xyz@gmail.com \
--cc=kevink@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.org \
/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.