All of lore.kernel.org
 help / color / mirror / Atom feed
From: alex.shi@linaro.org (Alex Shi)
To: linux-arm-kernel@lists.infradead.org
Subject: LSK merge linux-stable review
Date: Sat, 11 Jan 2014 09:35:52 +0800	[thread overview]
Message-ID: <52D09FF8.8060308@linaro.org> (raw)
In-Reply-To: <20140110163239.GF925@arm.com>


>>
>> the first column '-/+' means contents was removed/added from file
>> 5e9d274. the 2nd column '-/+' means contents was removed/added from file
>> 9c93e12.
>>
>> Yes, The notify_cpu_starting kept in final file later.
> 
> Just make sure it is in line with commit 7ade67b5984d0a (arm64: move
> enabling of GIC before CPUs are set online)
> 

Give you the part of modified smp.c file here :)
====

        printk("CPU%u: Booted secondary processor\n", cpu);

        /*
         * All kernel threads share the same mm context; grab a
         * reference and switch to it.
         */
        atomic_inc(&mm->mm_count);
        current->active_mm = mm;
        cpumask_set_cpu(cpu, mm_cpumask(mm));

        /*
         * TTBR0 is only used for the identity mapping at this stage. Make it
         * point to zero page to avoid speculatively fetching new entries.
         */
        cpu_set_reserved_ttbr0();
        flush_tlb_all();

        preempt_disable();
        trace_hardirqs_off();

        if (cpu_ops[cpu]->cpu_postboot)
                cpu_ops[cpu]->cpu_postboot();

        smp_store_cpu_info(cpu);

        /*
         * OK, now it's safe to let the boot CPU continue.  Wait for
         * the CPU migration code to notice that the CPU is online
         * before we continue.
         */
        set_cpu_online(cpu, true);
        complete(&cpu_running);

        /*
         * Enable GIC and timers.
         */
        notify_cpu_starting(cpu);

        local_irq_enable();
        local_fiq_enable();

        /*
         * OK, it's off to the idle thread for us
         */
        cpu_startup_entry(CPUHP_ONLINE);
}

-- 
Thanks
    Alex

  reply	other threads:[~2014-01-11  1:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140110013011.GA6447@alex-shi>
     [not found] ` <52CF61CC.40305@linaro.org>
2014-01-10 10:56   ` LSK merge linux-stable review Catalin Marinas
2014-01-10 15:31     ` Alex Shi
2014-01-10 16:32       ` Catalin Marinas
2014-01-11  1:35         ` Alex Shi [this message]
2014-01-13 15:55           ` Catalin Marinas
2014-01-14  0:32             ` Alex Shi
2014-01-14  9:45               ` Catalin Marinas
2014-01-14 10:20                 ` Alex Shi
     [not found]   ` <CADRr18M=sNsSD1PtoPeQw+DuQtn=p2uwFOLjEE-ztea3SnFHEQ@mail.gmail.com>
2014-01-10 15:51     ` Alex Shi
2014-01-10 15:53       ` Alex Shi

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=52D09FF8.8060308@linaro.org \
    --to=alex.shi@linaro.org \
    --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.