All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "Raj, Ashok" <ashok.raj@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Mihai Carabas <mihai.carabas@oracle.com>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
	Jon Grimm <Jon.Grimm@amd.com>,
	kanth.ghatraju@oracle.com, konrad.wilk@oracle.com,
	patrick.colp@oracle.com, Tom Lendacky <thomas.lendacky@amd.com>,
	x86-ml <x86@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/microcode: Add an option to reload microcode even if revision is unchanged
Date: Fri, 6 Sep 2019 09:46:55 +0200	[thread overview]
Message-ID: <20190906074655.GA19008@zn.tnic> (raw)
In-Reply-To: <20190905222706.GA4422@otc-nc-03>

On Thu, Sep 05, 2019 at 03:27:06PM -0700, Raj, Ashok wrote:
> Several customers have asked this to check the safety of late loads.
> They want to validate in production setup prior to rolling late-load
> to all production systems.

First of all, they should use *early* loading. I don't know how many
times I need to say that, maybe I should print it on T-shirts.

And then they can reboot. If you're thinking of the
"we-can't-reboot-because-we're-cloud" argument don't even bother to
bring it - I've had it more than enough and no, just because cloud
people don't want to reboot, it doesn't mean we will support some insane
use case.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2019-09-06  7:47 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29  5:33 [PATCH] x86/microcode: Add an option to reload microcode even if revision is unchanged Ashok Raj
2019-08-29  5:38 ` Raj, Ashok
2019-08-29  6:09 ` Borislav Petkov
2019-08-29 13:02   ` Raj, Ashok
2019-09-03 16:46     ` Borislav Petkov
2019-09-04 22:06       ` Boris Ostrovsky
2019-09-04 22:12         ` Boris Petkov
2019-09-05  0:21           ` Raj, Ashok
2019-09-05  7:20             ` Borislav Petkov
2019-09-05 10:51               ` Thomas Gleixner
2019-09-05 19:40               ` Raj, Ashok
2019-09-05 19:49                 ` Borislav Petkov
2019-09-05 20:20                   ` Raj, Ashok
2019-09-05 21:22                 ` Thomas Gleixner
2019-09-05 22:27                   ` Raj, Ashok
2019-09-06  7:46                     ` Borislav Petkov [this message]
2019-09-06 12:51                     ` Thomas Gleixner
2019-09-06 14:40                       ` Johannes Erdfelt
2019-09-06 15:16                         ` Borislav Petkov
2019-09-06 15:46                           ` Johannes Erdfelt
2019-09-06 16:17                             ` Borislav Petkov
2019-09-06 16:43                               ` Konrad Rzeszutek Wilk
2019-09-06 17:10                                 ` Borislav Petkov
2019-09-06 16:52                               ` Johannes Erdfelt
2019-09-06 17:17                                 ` Borislav Petkov
2019-09-06 21:16                         ` Thomas Gleixner
2019-09-07  0:33                           ` Raj, Ashok
2019-09-07 10:37                             ` Thomas Gleixner
2019-09-16 10:36                               ` Thomas Gleixner
2019-09-17  0:31                                 ` Raj, Ashok
2019-09-17  6:37                                   ` Thomas Gleixner
2019-09-17  6:46                                     ` Borislav Petkov
2019-09-17 14:29                                     ` Raj, Ashok
2019-09-19 19:48                           ` Mihai Carabas
2019-09-06 16:55                       ` Raj, Ashok

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=20190906074655.GA19008@zn.tnic \
    --to=bp@alien8.de \
    --cc=Jon.Grimm@amd.com \
    --cc=ashok.raj@intel.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=hpa@zytor.com \
    --cc=kanth.ghatraju@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mihai.carabas@oracle.com \
    --cc=mingo@redhat.com \
    --cc=patrick.colp@oracle.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --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.