mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Cc: <mingo@elte.hu>, "Stratos Psomadakis" <psomas@gentoo.org>,
	<stable@kernel.org>, <tj@kernel.org>, <tglx@linutronix.de>,
	<linux-kernel@vger.kernel.org>, <hpa@zytor.com>
Subject: Re: [PATCH] i386/bigsmp: eliminate false warnings regarding logical APIC ID mismatches
Date: Tue, 27 Sep 2011 09:57:47 +0100	[thread overview]
Message-ID: <4E81AC2B0200007800057F62@nat28.tlf.novell.com> (raw)
In-Reply-To: <20110926161353.GA3900@phenom.oracle.com>

>>> On 26.09.11 at 18:13, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
>> >> --- 3.1-rc2/arch/x86/kernel/apic/probe_32.c
>> >> +++ 3.1-rc2-i386-bigsmp-early-lapicid-override/arch/x86/kernel/apic/probe_32.c
>> >> @@ -203,7 +203,18 @@ void __init default_setup_apic_routing(v
>> >>  	if (!cmdline_apic && apic == &apic_default) {
>> >>  		struct apic *bigsmp = generic_bigsmp_probe();
>> >>  		if (bigsmp) {
>> >> +			unsigned int cpu;
>> >> +
>> >>  			apic = bigsmp;
>> >> +			for_each_possible_cpu(cpu) {
>> >> +				if (early_per_cpu(x86_cpu_to_logical_apicid,
>> >> +						  cpu) == BAD_APICID)
>> >> +					continue;
>> >> +				early_per_cpu(x86_cpu_to_logical_apicid,
>> >> +					      cpu) =
>> >> +					bigsmp->x86_32_early_logical_apicid
>> >> +						(cpu);
>> >> +			}
>> >>  			printk(KERN_INFO "Overriding APIC driver with %s\n",
>> >>  			       apic->name);
>> >>  		}
>> > Will this patch be included in 3.1 (so that it gets merged in 3.0-stable
>> > kernels sooner too) or will it go for 3.2?
>> 
>> That can only be answered by the maintainers (on Cc), not me - afaict
>> it didn't even get applied to -tip yet.
> 
> ping?

I haven't seen any tipbot for it (despite having re-sent it about two
weeks ago), so I have to assume it still didn't go in. I also didn't see
anything else (e.g. reasons why this shouldn't get applied), just
complete silence (I would almost say as "usual", no matter how hard
I try to meet Ingo's expectations on patch descriptions).

So I can only again defer answering your question to the maintainers,
who are all on Cc.

Jan


  reply	other threads:[~2011-09-27  8:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18 12:54 Jan Beulich
2011-08-18 13:04 ` Tejun Heo
2011-08-18 13:58   ` Jan Beulich
2011-08-18 14:02     ` Tejun Heo
2011-08-18 15:10       ` Jan Beulich
2011-08-18 15:15         ` Tejun Heo
2011-08-29 10:18 ` Stratos Psomadakis
2011-09-05  8:05   ` Jan Beulich
2011-09-26 16:13     ` Konrad Rzeszutek Wilk
2011-09-27  8:57       ` Jan Beulich [this message]
2011-09-27 13:35 ` Ingo Molnar
2011-09-27 14:39   ` Jan Beulich
2011-09-27 14:42     ` Ingo Molnar
2011-09-15  8:30 Jan Beulich

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=4E81AC2B0200007800057F62@nat28.tlf.novell.com \
    --to=jbeulich@suse.com \
    --cc=hpa@zytor.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=psomas@gentoo.org \
    --cc=stable@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®