All of lore.kernel.org
 help / color / mirror / Atom feed
From: ethan zhao <ethan.zhao@oracle.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Ethan Zhao <ethan.kernel@gmail.com>,
	tony.luck@intel.com, Thomas Gleixner <tglx@linutronix.de>,
	mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
	linux-edac@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	tim.uglow@oracle.com
Subject: Re: [PATCH] x86/mce: fix mce_restart() race with CPU hotplug operation
Date: Mon, 04 May 2015 08:34:32 +0800	[thread overview]
Message-ID: <5546BE98.5030208@oracle.com> (raw)
In-Reply-To: <20150503093757.GD18048@pd.tnic>

Borislav,
On 2015/5/3 17:37, Borislav Petkov wrote:
> On Fri, May 01, 2015 at 02:03:48PM +0800, Ethan Zhao wrote:
>>> For the record, it is a public secret that CPU hotplug is broken. IOW,
>>> you're wasting your time with those senseless pounder tests but ok.
>>    :<,  Someone else is stressing the CPU hotplug, seems it is fragile.
>> My job is holding the system, not panic to the ground.
> Please forward my message to that someone else then. The whole world
  Got it.

  Thanks,
  Ethan
> knows CPU hotplug is fragile and there are people working on improving
> that. There's no need for you guys to pound on it, we know it is broken.
> I'm sure you can find a lot other things in the kernel to pound on.
> Things which make a lot more sense than CPU hotplug.
>
> Thanks.
>


      reply	other threads:[~2015-05-04  0:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29 15:04 [PATCH] x86/mce: fix mce_restart() race with CPU hotplug operation Ethan Zhao
2015-04-30 16:29 ` Borislav Petkov
2015-05-01  5:54   ` Ethan Zhao
2015-05-01  6:03   ` Ethan Zhao
2015-05-03  9:37     ` Borislav Petkov
2015-05-04  0:34       ` ethan zhao [this message]

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=5546BE98.5030208@oracle.com \
    --to=ethan.zhao@oracle.com \
    --cc=bp@alien8.de \
    --cc=ethan.kernel@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tim.uglow@oracle.com \
    --cc=tony.luck@intel.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.