All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <ffainelli@freebox.fr>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH V2 8/8] MIPS: BMIPS: Add SMP support code for BMIPS43xx/BMIPS5000
Date: Sat, 12 Nov 2011 15:31:31 +0100	[thread overview]
Message-ID: <201111121531.31483.ffainelli@freebox.fr> (raw)
In-Reply-To: <3989f772f7fef3b4937ab01fd3af192e@localhost>

Hello Kevin,

Le vendredi 11 novembre 2011 07:30:31, Kevin Cernekee a écrit :
> Initial commit of BMIPS SMP support code.  Smoke-tested on a variety of
> BMIPS4350, BMIPS4380, and BMIPS5000 platforms.
> 
> Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
> ---
> 
> V2:
> 
> Move XKS01 option into this patch.
> 
> Remove dependency on local_flush_tlb_all_mm(), per the discussion
> earlier this week.
> 
> Allow platform-configurable variables to be accessed in !CONFIG_SMP
> mode, so the platform code does not need unnecessary #ifdefs.
> 
> Remove the code that clears the FPU registers.
> 
> Fix the jump to the NMI vector.
> 
> Add bmips_cpu_offset.

I have two questions regarding this patchset:

- considering that BMIPS4350 has a shared TLB, is it still working fine? I must 
say that I have not yet tested on e.g: BCM6358

- there a couple of places in the code where we have:

#if defined (CONFIG_BMIPS_4350) || defined (CONFIG_BMIPS_4380)
 ... do something
#elif defined(CONFIG_BMIPS_4380)

can we turn this into a #if BMIPS43xx case .. #endif  #if BMIPS5000 ... #endif 
to allow a single image supporting both BMIPS43xx and BMIPS5000?

By the time we are initializing the CPUs for SMP, we should be able to use 
runtime checks on the BMIPS CPU variant.

Thanks.
-- 
Florian

  parent reply	other threads:[~2011-11-12 14:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11  6:30 [PATCH V2 1/8] MIPS: BMIPS: Fix up Kconfig settings Kevin Cernekee
2011-11-11  6:30 ` [PATCH V2 2/8] MIPS: Clean up whitespace warning in hazards.h Kevin Cernekee
2011-11-11 18:03   ` Ralf Baechle
2011-11-11  6:30 ` [PATCH V2 3/8] MIPS: BMIPS: Add CFLAGS, Makefile entries for BMIPS Kevin Cernekee
2011-11-11 12:58   ` Ralf Baechle
2011-11-11 16:57     ` Kevin Cernekee
2011-11-11 17:20       ` Ralf Baechle
2011-11-12 14:11         ` Florian Fainelli
2011-11-11 18:03       ` Ralf Baechle
2011-11-11  6:30 ` [PATCH V2 4/8] MIPS: BMIPS: Add set/clear CP0 macros for BMIPS operations Kevin Cernekee
2011-11-11 18:04   ` Ralf Baechle
2011-11-11  6:30 ` [PATCH V2 5/8] MIPS: BMIPS: Introduce bmips.h Kevin Cernekee
2011-11-11 13:32   ` Ralf Baechle
2011-11-11 18:04   ` Ralf Baechle
2011-11-11  6:30 ` [PATCH V2 6/8] MIPS: Add NMI notifier Kevin Cernekee
2011-11-11 13:34   ` Ralf Baechle
2011-11-11 18:04   ` Ralf Baechle
2011-11-11  6:30 ` [PATCH V2 7/8] MIPS: Add board_ebase_setup() Kevin Cernekee
2011-11-11 18:05   ` Ralf Baechle
2011-11-11  6:30 ` [PATCH V2 8/8] MIPS: BMIPS: Add SMP support code for BMIPS43xx/BMIPS5000 Kevin Cernekee
2011-11-11 18:05   ` Ralf Baechle
2011-11-12 14:31   ` Florian Fainelli [this message]
2011-11-12 16:07     ` Kevin Cernekee
2011-11-11 18:03 ` [PATCH V2 1/8] MIPS: BMIPS: Fix up Kconfig settings 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=201111121531.31483.ffainelli@freebox.fr \
    --to=ffainelli@freebox.fr \
    --cc=cernekee@gmail.com \
    --cc=linux-mips@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.