From: Eial Czerwacki <eial@scalemp.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Randy Dunlap <rdunlap@infradead.org>
Cc: "Shai Fultheim (Shai@ScaleMP.com)" <Shai@ScaleMP.com>,
Andrew Morton <akpm@linux-foundation.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"mhocko@suse.cz" <mhocko@suse.cz>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
"mm-commits@vger.kernel.org" <mm-commits@vger.kernel.org>,
X86 ML <x86@kernel.org>, 'Oren Twaig' <oren@scalemp.com>
Subject: Re: [PATCH] x86/build: Build VSMP support only if selected
Date: Thu, 1 Nov 2018 15:10:35 +0200 [thread overview]
Message-ID: <a8f2ac8e-45dc-1c12-e888-6ad880b1306f@scalemp.com> (raw)
In-Reply-To: <SN6PR15MB2366D7688B41535AF0A331F9C3CE0@SN6PR15MB2366.namprd15.prod.outlook.com>
Greetings,
On 11/01/2018 12:39 PM, Shai Fultheim (Shai@ScaleMP.com) wrote:
> On 01/11/18 11:37, Thomas Gleixner wrote:
>
>> VSMP support is built even if CONFIG_X86_VSMP is not set. This leads to a build
>> breakage when CONFIG_PCI is disabled as well.
>>
>> Build VSMP code only when selected.
>
> This patch disables detect_vsmp_box() on systems without CONFIG_X86_VSMP, due to
> the recent 6da63eb241a05b0e676d68975e793c0521387141. This is significant
> regression that will affect significant number of deployments.
>
> We will reply shortly with an updated patch that fix the dependency on pv_irq_ops,
> and revert to CONFIG_PARAVIRT, with proper protection for CONFIG_PCI.
>
here is the proper patch which fixes the issue on hand:
next prev parent reply other threads:[~2018-11-01 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 23:09 mmotm 2018-10-30-16-08 uploaded akpm
2018-10-31 3:20 ` mmotm 2018-10-30-16-08 uploaded (arch/x86/kernel/vsmp_64.c) Randy Dunlap
2018-11-01 9:36 ` [PATCH] x86/build: Build VSMP support only if selected Thomas Gleixner
2018-11-01 10:39 ` Shai Fultheim (Shai@ScaleMP.com)
2018-11-01 13:10 ` Eial Czerwacki [this message]
2018-11-01 13:17 ` Thomas Gleixner
2018-11-01 13:45 ` Juergen Gross
2018-11-01 15:09 ` Eial Czerwacki
2018-11-01 15:39 ` Juergen Gross
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=a8f2ac8e-45dc-1c12-e888-6ad880b1306f@scalemp.com \
--to=eial@scalemp.com \
--cc=Shai@ScaleMP.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=oren@scalemp.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--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