All of lore.kernel.org
 help / color / mirror / Atom feed
From: Toshi Kani <toshi.kani@hp.com>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
	tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	bp@alien8.de, gong.chen@linux.intel.com, tony.luck@intel.com,
	x86@kernel.org, imammedo@redhat.com, huawei.libin@huawei.com,
	paul.gortmaker@windriver.com, linux-kernel@vger.kernel.org,
	srivatsa.bhat@linux.vnet.ibm.com, peterz@infradead.org,
	Wanpeng Li <wanpeng.li@linux.intel.com>,
	Linn Crosetto <linn@hp.com>
Subject: Re: [PATCH v5] x86,cpu-hotplug: assign same CPU number to readded CPU
Date: Mon, 15 Sep 2014 10:44:23 -0600	[thread overview]
Message-ID: <1410799463.28990.326.camel@misato.fc.hp.com> (raw)
In-Reply-To: <1410755159.5165.24.camel@marge.simpson.net>

On Mon, 2014-09-15 at 06:25 +0200, Mike Galbraith wrote:
> On Thu, 2014-09-11 at 16:21 +0900, Yasuaki Ishimatsu wrote: 
> > There is no response for two months since posting v4.
> > What can I do for pushing the patch to upstream?
> 
> Looks to me like we have two patches floating about for more or less the
> same problem, this one, and...
> 
> https://lkml.org/lkml/2014/7/29/159
> 
> ..this one, which you reviewed, and HP both reviewed and tested.
> 
> We seem to kinda stuck with Boris having said don't diddle the
> cpu_llc_shared_map, but HP/Intel saying that this map diddling fixes
> their explosions.  If your alternative is preferred over diddling
> cpu_llc_shared_map, perhaps HP/Intel can test/confirm that their
> explosions stay gone? 

Well, Boris mentioned later in his email:
https://lkml.org/lkml/2014/7/22/201

And I agree with his assessment that both patches make sense.  

Thanks,
-Toshi



  reply	other threads:[~2014-09-15 16:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23  3:22 [PATCH v4] x86,cpu-hotplug: assign same CPU number to readded CPU Yasuaki Ishimatsu
2014-07-28  4:18 ` Yasuaki Ishimatsu
2014-09-04  2:46   ` [PATCH v5] " Yasuaki Ishimatsu
2014-09-11  7:21     ` Yasuaki Ishimatsu
2014-09-15  4:25       ` Mike Galbraith
2014-09-15 16:44         ` Toshi Kani [this message]
2014-09-16  3:56           ` Mike Galbraith
2014-09-16  9:53             ` Wanpeng Li
2014-09-16 10:00               ` Mike Galbraith

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=1410799463.28990.326.camel@misato.fc.hp.com \
    --to=toshi.kani@hp.com \
    --cc=bp@alien8.de \
    --cc=gong.chen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=huawei.libin@huawei.com \
    --cc=imammedo@redhat.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=linn@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=peterz@infradead.org \
    --cc=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=umgwanakikbuti@gmail.com \
    --cc=wanpeng.li@linux.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.