All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolai Stange <nicstange@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Nicolai Stange <nicstange@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch/x86/kernel/cpu/microcode/intel: don't store initrd's start
Date: Mon, 25 Jul 2016 19:44:10 +0200	[thread overview]
Message-ID: <871t2hd34l.fsf@gmail.com> (raw)
In-Reply-To: <20160725164602.GC11976@nazgul.tnic> (Borislav Petkov's message of "Mon, 25 Jul 2016 18:46:02 +0200")

Borislav Petkov <bp@alien8.de> writes:
> Yeah, we should tie this to CONFIG_RANDOMIZE_MEMORY. IOW, here's another
> version, I'll do some more hammering on it tomorrow.

Boots fine and updates microcode (as always, on top of next-20160722).


> It should take care of the builtin case too as there we have the
> microcode in the kernel text mapping which is already relocated when we
> go search for microcode blobs so no need for adjusting start then.

Now that you've got basically the same #ifdefery and if(->valid)'s in
your final result as I did, may I ask whether you would still consider
it as being simpler? In particular, what's the point of having that
->start if it's redundant and has to be corrected in a more or less
hackish way anyway?

Thanks,

Nicolai

  reply	other threads:[~2016-07-25 17:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-24 15:05 [PATCH] arch/x86/kernel/cpu/microcode/intel: don't store initrd's start Nicolai Stange
2016-07-25  7:06 ` Borislav Petkov
2016-07-25  9:24   ` Nicolai Stange
2016-07-25 12:36     ` Borislav Petkov
2016-07-25 12:59       ` Nicolai Stange
2016-07-25 13:06         ` Nicolai Stange
2016-07-25 13:44         ` Borislav Petkov
2016-07-25 14:16           ` Nicolai Stange
2016-07-25 14:27             ` Nicolai Stange
2016-07-25 16:40               ` Borislav Petkov
2016-07-25 15:07             ` Borislav Petkov
2016-07-25 16:46             ` Borislav Petkov
2016-07-25 17:44               ` Nicolai Stange [this message]
2016-07-25 18:18                 ` Borislav Petkov

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=871t2hd34l.fsf@gmail.com \
    --to=nicstange@gmail.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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.