mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
	<linux-snps-arc@lists.infradead.org>
Cc: <linux-kernel@vger.kernel.org>,
	Vineet Gupta <Vineet.Gupta1@synopsys.com>
Subject: Re: [PATCH] ARC: Enable machine_desc->init_per_cpu for non-SMP configs
Date: Thu, 30 Nov 2017 09:46:26 -0800	[thread overview]
Message-ID: <ee663800-7f72-c310-2a65-d8b52a811f15@synopsys.com> (raw)
In-Reply-To: <20171129082145.23327-1-abrodkin@synopsys.com>

On 11/29/2017 12:21 AM, Alexey Brodkin wrote:
> As of today we assumed that "machine_desc->init_per_cpu" calls
> are only usable on SMP systems when we want to run some piece of
> code on early boot for each and every core, I guess assumption was
> we have "machine_desc->init_early" for single-core cases where
> the one and only master core can do all the things.
> 
> But it turned out for platforms which might be both UP and SMP it
> might be benificial to use "init_per_cpu" for both UP and SMP cases
> with which we achieve 2 things simultaneously:
>   1) Exactly the same one code will be used for UP&SMP for
>      things required to be done on each an every core regardless if it's
>      a master and the only core in UP system or any other slave core in SMP
>      setup.
>   1) There will be no "ifdef CONFIG_SMP" around "init_per_cpu".
> 

Seems fine to me. However this needs to go with the actual platform change which 
needs it.

-Vineet

  reply	other threads:[~2017-11-30 17:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29  8:21 Alexey Brodkin
2017-11-30 17:46 ` Vineet Gupta [this message]
2018-06-14 22:26   ` Alexey Brodkin
2018-06-20 23:11     ` Vineet Gupta

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=ee663800-7f72-c310-2a65-d8b52a811f15@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®