All of lore.kernel.org
 help / color / mirror / Atom feed
From: nyushchenko@dev.rtsoft.ru (Nikita Yushchenko)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC/PATCH] arm: do not skip SMP init calls on SMP_ON_UP case
Date: Mon, 23 Nov 2015 15:46:00 +0300	[thread overview]
Message-ID: <56530A88.5010408@dev.rtsoft.ru> (raw)
In-Reply-To: <20151123121920.GP8644@n2100.arm.linux.org.uk>

23.11.2015 15:19, Russell King - ARM Linux ?????:
> On Mon, Nov 23, 2015 at 12:12:16PM +0000, Russell King - ARM Linux wrote:
>> iMX6 is fairly well supported in mainline.  The only reason to use a
>> custom kernel is if you want to use some feature which mainline does
>> not support (or support very well) such as video decode, the full IPU
>> facilities, GPUs or CEC (sorry, I don't have an expansive list.)
>>
>> The GPU problem for the GC320/GC880/GC2000 is fairly close to being
>> solved in a functional (but maybe not yet performant) manner.
> 
> For reference, iMX6S in mainline behaves like this:
> 
> Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=12000)
> pid_max: default: 32768 minimum: 301
> Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
> Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
> Initializing cgroup subsys net_cls
> CPU: Testing write buffer coherency: ok
> CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
> Setting up static identity map for 0x100082c0 - 0x10008318
> Brought up 1 CPUs
> SMP: Total of 1 processors activated (6.00 BogoMIPS).
> CPU: All CPU(s) started in SVC mode.

Indeed, somehow booted mainline and it does not try to initialize CPU 1.

WARNING: multiple messages have this Message-ID (diff)
From: Nikita Yushchenko <nyushchenko@dev.rtsoft.ru>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: kuznetsovg@dev.rtsoft.ru, Ian Campbell <ian.campbell@citrix.com>,
	Mason <slash.tmp@free.fr>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Will Deacon <will.deacon@arm.com>,
	Paul Kocialkowski <contact@paulk.fr>,
	linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC/PATCH] arm: do not skip SMP init calls on SMP_ON_UP case
Date: Mon, 23 Nov 2015 15:46:00 +0300	[thread overview]
Message-ID: <56530A88.5010408@dev.rtsoft.ru> (raw)
In-Reply-To: <20151123121920.GP8644@n2100.arm.linux.org.uk>

23.11.2015 15:19, Russell King - ARM Linux пишет:
> On Mon, Nov 23, 2015 at 12:12:16PM +0000, Russell King - ARM Linux wrote:
>> iMX6 is fairly well supported in mainline.  The only reason to use a
>> custom kernel is if you want to use some feature which mainline does
>> not support (or support very well) such as video decode, the full IPU
>> facilities, GPUs or CEC (sorry, I don't have an expansive list.)
>>
>> The GPU problem for the GC320/GC880/GC2000 is fairly close to being
>> solved in a functional (but maybe not yet performant) manner.
> 
> For reference, iMX6S in mainline behaves like this:
> 
> Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=12000)
> pid_max: default: 32768 minimum: 301
> Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
> Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
> Initializing cgroup subsys net_cls
> CPU: Testing write buffer coherency: ok
> CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
> Setting up static identity map for 0x100082c0 - 0x10008318
> Brought up 1 CPUs
> SMP: Total of 1 processors activated (6.00 BogoMIPS).
> CPU: All CPU(s) started in SVC mode.

Indeed, somehow booted mainline and it does not try to initialize CPU 1.


  reply	other threads:[~2015-11-23 12:46 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 11:59 [RFC/PATCH] arm: do not skip SMP init calls on SMP_ON_UP case nyushchenko at dev.rtsoft.ru
2015-11-23 11:59 ` nyushchenko
2015-11-23 12:03 ` Russell King - ARM Linux
2015-11-23 12:03   ` Russell King - ARM Linux
2015-11-23 12:06   ` Nikita Yushchenko
2015-11-23 12:06     ` Nikita Yushchenko
2015-11-23 12:12     ` Russell King - ARM Linux
2015-11-23 12:12       ` Russell King - ARM Linux
2015-11-23 12:19       ` Russell King - ARM Linux
2015-11-23 12:19         ` Russell King - ARM Linux
2015-11-23 12:46         ` Nikita Yushchenko [this message]
2015-11-23 12:46           ` Nikita Yushchenko
2015-11-23 12:32     ` Vladimir Murzin
2015-11-23 12:32       ` Vladimir Murzin
2015-11-23 12:42       ` Nikita Yushchenko
2015-11-23 12:42         ` Nikita Yushchenko
2015-11-23 12:47         ` Nikita Yushchenko
2015-11-23 12:47           ` Nikita Yushchenko
2015-11-23 13:04           ` Russell King - ARM Linux
2015-11-23 13:04             ` Russell King - ARM Linux
2015-11-24 14:52             ` Nikita Yushchenko
2015-11-24 14:52               ` Nikita Yushchenko
2015-11-24 15:05               ` Nikita Yushchenko
2015-11-24 15:05                 ` Nikita Yushchenko
2015-11-24 15:28                 ` Nikita Yushchenko
2015-11-24 15:28                   ` Nikita Yushchenko
2015-11-24 15:33               ` Russell King - ARM Linux
2015-11-24 15:33                 ` Russell King - ARM Linux
2015-11-28 11:13                 ` Nikita Yushchenko
2015-11-28 11:13                   ` Nikita Yushchenko
2015-11-30  8:25                   ` Nikita Yushchenko
2015-11-30  8:25                     ` Nikita Yushchenko

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=56530A88.5010408@dev.rtsoft.ru \
    --to=nyushchenko@dev.rtsoft.ru \
    --cc=linux-arm-kernel@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 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.