From: Ingo Molnar <mingo@kernel.org>
To: Juergen Gross <jgross@suse.com>
Cc: Prarit Bhargava <prarit@redhat.com>,
Dou Liyang <douly.fnst@cn.fujitsu.com>,
Andi Kleen <ak@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
x86@kernel.org, linux-kernel@vger.kernel.org,
simon@invisiblethingslab.com,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Ingo Molnar <mingo@redhat.com>, Andy Lutomirski <luto@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>
Subject: Re: [PATCH] x86/xen: Calculate __max_logical_packages on PV domains
Date: Tue, 13 Feb 2018 13:29:20 +0100 [thread overview]
Message-ID: <20180213122920.4afcvqqxcstbftan@gmail.com> (raw)
In-Reply-To: <0e2775c8-2114-e554-dd0f-7222300e3e27@suse.com>
* Juergen Gross <jgross@suse.com> wrote:
> On 08/02/18 01:59, Boris Ostrovsky wrote:
> >
> >
> > On 02/07/2018 06:49 PM, Prarit Bhargava wrote:
> >> The kernel panics on PV domains because native_smp_cpus_done() is
> >> only called for HVM domains.
> >>
> >> Calculate __max_logical_packages for PV domains.
> >>
> >> Fixes: b4c0a7326f5d ("x86/smpboot: Fix __max_logical_packages estimate")
> >> Signed-off-by: Prarit Bhargava <prarit@redhat.com>
> >> Tested-and-reported-by: Simon Gaiser <simon@invisiblethingslab.com>
> >> Cc: Thomas Gleixner <tglx@linutronix.de>
> >> Cc: Ingo Molnar <mingo@redhat.com>
> >> Cc: "H. Peter Anvin" <hpa@zytor.com>
> >> Cc: x86@kernel.org
> >> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> >> Cc: Juergen Gross <jgross@suse.com>
> >> Cc: Dou Liyang <douly.fnst@cn.fujitsu.com>
> >> Cc: Prarit Bhargava <prarit@redhat.com>
> >> Cc: Kate Stewart <kstewart@linuxfoundation.org>
> >> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >> Cc: Andy Lutomirski <luto@kernel.org>
> >> Cc: Andi Kleen <ak@linux.intel.com>
> >> Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
> >> Cc: xen-devel@lists.xenproject.org
> >
> >
> > Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>
> Thomas, Ingo, are you taking this via the tip tree or should I take
> it via the xen tree?
Since it's supposed to only affect Xen feel free to pick it up:
Acked-by: Ingo Molnar <mingo@kernel.org>
Thanks,
Ingo
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-02-13 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180207234923.13544-1-prarit@redhat.com>
2018-02-08 0:59 ` [PATCH] x86/xen: Calculate __max_logical_packages on PV domains Boris Ostrovsky
[not found] ` <5607eaea-5cc3-31a4-9685-1d7dd147f564@oracle.com>
2018-02-08 8:49 ` Juergen Gross
[not found] ` <0e2775c8-2114-e554-dd0f-7222300e3e27@suse.com>
2018-02-13 12:29 ` Ingo Molnar [this message]
2018-02-27 17:08 ` Simon Gaiser
2018-02-12 13:51 ` Juergen Gross
2018-02-07 23:49 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=20180213122920.4afcvqqxcstbftan@gmail.com \
--to=mingo@kernel.org \
--cc=ak@linux.intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=prarit@redhat.com \
--cc=simon@invisiblethingslab.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).