From: Michael Ellerman <michael@ellerman•id.au>
To: Alexey Kardashevskiy <aik@ozlabs•ru>
Cc: Preeti U Murthy <preeti@linux•vnet.ibm.com>,
"Shreyas B. Prabhu" <shreyas@linux•vnet.ibm.com>,
"linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>,
Anton Blanchard <anton@samba•org>,
Paul Mackerras <paulus@samba•org>
Subject: Re: offlining cpus breakage
Date: Fri, 16 Jan 2015 14:04:42 +1100 [thread overview]
Message-ID: <1421377482.18166.5.camel@ellerman.id.au> (raw)
In-Reply-To: <54B85B3C.1030000@ozlabs.ru>
On Fri, 2015-01-16 at 13:28 +1300, Alexey Kardashevskiy wrote:
> On 01/16/2015 02:22 AM, Preeti U Murthy wrote:
> > Hi Alexey,
> >
> > Can you let me know if the following patch fixes the issue for you ?
> > It did for us on one of our machines that we were investigating on.
>
> This fixes the issue for me as well, thanks!
>
> Tested-by: Alexey Kardashevskiy <aik@ozlabs•ru>
OK, that's great.
But, I really don't think we can ask upstream to merge this patch to generic
code when we don't have a good explanation for why it's necessary. At least I'm
not going to ask anyone to do that :)
So Pretti can you either write a 100% convincing explanation of why this patch
is correct in the general case, or (preferably) do some more investigating to
work out what Alexey's bug actually is.
cheers
next prev parent reply other threads:[~2015-01-16 3:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 9:37 offlining cpus breakage Alexey Kardashevskiy
2015-01-14 4:20 ` Shreyas B Prabhu
2015-01-14 11:03 ` Shreyas B Prabhu
2015-01-15 13:22 ` Preeti U Murthy
2015-01-16 0:28 ` Alexey Kardashevskiy
2015-01-16 3:04 ` Michael Ellerman [this message]
2015-01-16 8:56 ` Preeti U Murthy
2015-01-16 9:10 ` Preeti U Murthy
2015-01-22 5:29 ` Michael Ellerman
2015-01-22 6:31 ` Preeti U Murthy
2015-01-17 13:39 ` Preeti U Murthy
2015-01-18 16:50 ` Preeti U Murthy
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=1421377482.18166.5.camel@ellerman.id.au \
--to=michael@ellerman$(echo .)id.au \
--cc=aik@ozlabs$(echo .)ru \
--cc=anton@samba$(echo .)org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=paulus@samba$(echo .)org \
--cc=preeti@linux$(echo .)vnet.ibm.com \
--cc=shreyas@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox