[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [XEN PATCH v2 5/5] x86/MCE: optional build of AMD/Intel MCE code


  • To: Jan Beulich <jbeulich@xxxxxxxx>
  • From: Sergiy Kibrik <sergiy_kibrik@xxxxxxxx>
  • Date: Mon, 13 May 2024 12:11:26 +0300
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=epam.com; dmarc=pass action=none header.from=epam.com; dkim=pass header.d=epam.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=5KFEwE20wNiNRdhe7S74RnbY5GaK8qhweDQOMEVT7IQ=; b=Qw0d3jPlCiUa/E9Jm2esejCTtMVKERqBi1pDWijAkx/BocsGUYewPbwAfF8BXB/rJ8RaSUkzN8xa25vpZIROQuwws5AXhorAooNjxPud2Vj4/aovXDyYx9xkxueEmdd7fVmDPjt1xwHVCLbNXR4uWoqj9T1S1wCzsX0WSRsIIPUPJ8U5t86irqt6I2LcfmWjjcRxCCaDidqVo3a2E7VU0I8747tpw1OS7fT0t0B09Zh6IlE9S0mhC1s0B4OaK94rgrGFvRiY1Uvm6Id4Z7uTJBHmAhp4uFyNQzl7a1gASeypvyI9IcTSgNOOT1HjYD2WrlKHHbiKkpV4mFQPYgRA7Q==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZXLEMzQeJQTp6DQq2/fnMquD0jg83NA7Jm/eXDemoCXf/cooAMHa0yqVwpg+FC0nfuQQ60ui6VQf3oIh0pyF4cKtKBh1/48YRtCXtvJxSucoq/37QfplYWP73cwYbJ5veVdcGFq5mdvKVlAZQ9nyBRiZfSqvyqAqBQq4uH8CgrXwjSHbbev2Wvr+sqUQYDAWrlwNcgVGMf1n8GNdPyvUh6rMG/uMrQfdtZy7FPs5PXqmz+1FuEryGxGgPsjYjCL6iU4t8spX3TVE19NgnBj9bLC8TzVQpiJTO0ZqNOpV2WigcWsvoVJWpz0vYh/Jj3Dr+My0kGIS6HxjLduKi2deeQ==
  • Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 13 May 2024 09:12:06 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

06.05.24 14:32, Jan Beulich:
On 02.05.2024 11:21, Sergiy Kibrik wrote:
Separate Intel/AMD-specific MCE code using CONFIG_{INTEL,AMD} config options.
Now we can avoid build of mcheck code if support for specific platform is
intentionally disabled by configuration.

Add default return value to init_nonfatal_mce_checker() routine -- in case
of a build with both AMD and INTEL options are off (e.g. randconfig).

I'm afraid that, as before, I can't accept this as a justification for the
addition. The addition likely is wanted, but perhaps in a separate up-front
patch and explaining what's wrong when that's missing.

sure, I'll do separate patch for that.


Also global Intel-specific variables lmce_support & cmci_support have to be
redefined if !INTEL, as they get checked in common code.

Them being checked in common code may have different resolution strategies.
The justification here imo is that, right now, both variables are only ever
written by mce_intel.c. As mentioned for vmce_has_lmce(), there's nothing
fundamentally preventing MCG_CAP from having respective bits set on a non-
Intel CPU.


so could these global variables just be moved to common code then? Like arch/x86/cpu/mcheck/mce.c ?

  -Sergiy



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.