All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: Chunyu Hu <chuhu@redhat.com>, Ingo Molnar <mingo@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Borislav Petkov <bp@alien8.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/idt: load idt early in start_secondary
Date: Tue, 28 Nov 2017 08:17:43 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1711280817270.2333@nanos> (raw)
In-Reply-To: <CALCETrXepexpxHQdWj4taAxbmssbSeeuV6DJ7QGw1o2TfS1R4A@mail.gmail.com>

On Mon, 27 Nov 2017, Andy Lutomirski wrote:
> On Mon, Nov 27, 2017 at 8:57 PM, Chunyu Hu <chuhu@redhat.com> wrote:
> >> > To make WARN()s can work earlier to ap, we load the idt_table early
> >> > in start_secondary, and keep the second time idt load in cpu_init,
> >> > as there is a load_ucode_ap() there.
> >>
> >> Reviewed-by: Andy Lutomirski <luto@kernel.org>
> >>
> >> Except that this is presumably missing a Cc: stable.
> >
> > Do I need to resend this origin version and Cc stable?
> 
> I imagine that Ingo can add it.

Done.

  reply	other threads:[~2017-11-28  7:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 14:21 [PATCH] x86/idt: load idt early in start_secondary Chunyu Hu
2017-11-27 23:35 ` [tip:x86/urgent] x86/idt: Load " tip-bot for Chunyu Hu
2017-11-28  3:41 ` [PATCH] x86/idt: load " Andy Lutomirski
2017-11-28  4:57   ` Chunyu Hu
2017-11-28  5:28     ` Andy Lutomirski
2017-11-28  7:17       ` Thomas Gleixner [this message]
2017-11-28 14:56     ` Steven Rostedt
2017-11-28  7:22 ` [tip:x86/urgent] x86/idt: Load " tip-bot for Chunyu Hu

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=alpine.DEB.2.20.1711280817270.2333@nanos \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=chuhu@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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.