From: Marc St-Jean <Marc_St-Jean@pmc-sierra.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Thiemo Seufer <ths@networkno.de>,
Andrew Sharp <tigerand@gmail.com>,
linux-mips@linux-mips.org
Subject: Re: [PATCH 2/5] mips: PMC MSP71xx mips common
Date: Wed, 28 Feb 2007 14:35:59 -0800 [thread overview]
Message-ID: <45E603CF.506@pmc-sierra.com> (raw)
Ralf Baechle wrote:
> On Wed, Feb 28, 2007 at 01:35:32PM -0800, Marc St-Jean wrote:
>
> > Ralf Baechle wrote:
> > > On Tue, Feb 27, 2007 at 05:38:41PM +0000, Thiemo Seufer wrote:
> > >
> > > > Something like
> > > >
> > > > #if LOADADDR == 0xffffffff80000000
> > > > .fill 0x400
> > > > #endif
> > > >
> > > > but by defining an appropriate name in arch/mips/Makefile
> instead of
> > > > externalizing the load-y/LOADADDR there.
> > >
> > > Basically a good idea but it will fail for 64-bit kernels so the test
> > > would need to be extended to cover XKPHYS as well. Also R2 processors
> > > which have the c0_ebase registers do no need to reserve space for
> > > exception handlers as they can easily move them elsewhere.
> > >
> > > Ralf
> >
> > Hi Ralf,
> >
> > From your description it sounds like not all R2 CPUs have c0_ebase
> registers?
> >
> > I don't know how to check for c0_ebase from the pre-processor, the
> test below
> > assumes they all do.
>
> Sorry for being ambigous. All R2 processors have ebase. However Linux
> happens to support older processors as well, that was my point.
>
> > How about something like:
> >
> > #if (defined(CONFIG_SYS_HAS_CPU_MIPS32_R1) && \
> > VMLINUX_LOAD_ADDRESS == CKSEG0) || \
> > ((defined(CONFIG_SYS_HAS_CPU_MIPS64_R1) ||
> defined(CONFIG_SYS_HAS_CPU_MIPS64_R2)) && \
> > VMLINUX_LOAD_ADDRESS == XKPHYS)
> > .fill 0x400
> > #endif
>
> There are several potencial addresses in XKPHYS, so if anything:
>
> #if !defined(CONFIG_CPU_MIPSR2) && \
> ((VMLINUX_LOAD_ADDRESS == CKSEG0) || \
> (VMLINUX_LOAD_ADDRESS & 0xc7ffffffffffffffUL) == XKPHYS)
>
> However even where ebase actually exists there might be reasons not to use
> it. So a config option might be the safe thing to do.
>
> Ralf
OK, I'll introduce a CONFIG_NO_EXCEPT_FILL as proposed earlier and select
it in our platform configuration section.
Marc
next reply other threads:[~2007-02-28 22:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 22:35 Marc St-Jean [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-16 23:53 [PATCH 2/5] mips: PMC MSP71xx mips common Marc St-Jean
2007-03-17 0:46 ` Ralf Baechle
2007-03-07 18:01 Marc St-Jean
2007-03-16 1:58 ` Ralf Baechle
2007-03-01 20:41 Marc St-Jean
2007-02-28 21:35 Marc St-Jean
2007-02-28 21:43 ` Uhler, Mike
2007-02-28 21:43 ` Uhler, Mike
2007-02-28 22:18 ` Ralf Baechle
2007-02-28 0:04 Marc St-Jean
2007-02-27 21:27 Marc St-Jean
2007-02-28 19:52 ` Ralf Baechle
2007-02-27 17:59 Marc St-Jean
2007-02-27 20:03 ` Thiemo Seufer
2007-02-27 17:09 Marc St-Jean
2007-02-27 17:38 ` Thiemo Seufer
2007-02-28 19:32 ` Ralf Baechle
2007-02-27 18:46 ` Andrew Sharp
2007-02-28 19:42 ` Ralf Baechle
2007-02-27 0:12 Marc St-Jean
2007-02-27 0:43 ` Andrew Sharp
2007-02-23 21:27 Marc St-Jean
2007-02-23 21:15 Marc St-Jean
2007-02-23 20:53 Marc St-Jean
2007-02-23 21:02 ` Sergei Shtylyov
2007-02-23 21:02 ` David Daney
2007-02-23 19:56 Marc St-Jean
2007-02-23 20:35 ` Sergei Shtylyov
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=45E603CF.506@pmc-sierra.com \
--to=marc_st-jean@pmc-sierra.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=ths@networkno.de \
--cc=tigerand@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.