From: Thomas Gleixner <tglx@linutronix.de>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Prarit Bhargava <prarit@redhat.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
Len Brown <len.brown@intel.com>, Borislav Petkov <bp@suse.de>,
Andi Kleen <ak@linux.intel.com>, Juergen Gross <jgross@suse.com>,
dyoung@redhat.com, Eric Biederman <ebiederm@xmission.com>,
kexec@lists.infradead.org
Subject: Re: [PATCH] arch/x86: Fix kdump on x86 with physically hotadded CPUs
Date: Tue, 4 Oct 2016 16:19:59 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1610041618390.5049@nanos> (raw)
In-Reply-To: <20161004122717.GA4998@krava>
On Tue, 4 Oct 2016, Jiri Olsa wrote:
> On Tue, Oct 04, 2016 at 12:58:04PM +0200, Thomas Gleixner wrote:
> > > pmu->boxes[pkg] is garbage because pkg was returned as 0xffff.
> >
> > And that's what needs to be fixed in the first place.
>
> right, I'll check on that.. but I think we need this fix as well
That's right.
> I was wondering if acpi_boot_init was a better place for that, but then
> Prarit suggested in our discussion that the prefill_possible_map() call
> seems to be a hotplug cleanup.. so it seemed to fit
It's the right place for it.
Thanks,
tglx
next prev parent reply other threads:[~2016-10-04 14:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 17:07 [PATCH] arch/x86: Fix kdump on x86 with physically hotadded CPUs Prarit Bhargava
2016-10-03 22:22 ` Jiri Olsa
2016-10-04 10:58 ` Thomas Gleixner
2016-10-04 12:09 ` Prarit Bhargava
2016-10-04 14:38 ` Thomas Gleixner
2016-10-04 16:01 ` Prarit Bhargava
2016-10-05 16:14 ` Jiri Olsa
2016-10-06 15:25 ` Prarit Bhargava
2016-10-07 6:49 ` Jiri Olsa
2016-10-07 8:02 ` Thomas Gleixner
2016-10-04 12:27 ` Jiri Olsa
2016-10-04 14:19 ` Thomas Gleixner [this message]
2016-10-07 13:28 ` [tip:x86/urgent] arch/x86: Handle non enumerated CPU after physical hotplug tip-bot for Prarit Bhargava
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=alpine.DEB.2.20.1610041618390.5049@nanos \
--to=tglx@linutronix.de \
--cc=ak@linux.intel.com \
--cc=bp@suse.de \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jolsa@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=prarit@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox