All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Roger Pau Monné" <roger.pau@citrix.com>,
	Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 6/6] x86/apic: Convert the TSC deadline errata table to X86_MATCH_*()
Date: Thu, 17 Jul 2025 10:31:33 +0200	[thread overview]
Message-ID: <3e3df60f-be4f-451c-aeb9-12a8d490cdc2@suse.com> (raw)
In-Reply-To: <20250716173132.2213891-7-andrew.cooper3@citrix.com>

On 16.07.2025 19:31, Andrew Cooper wrote:
> --- a/xen/arch/x86/apic.c
> +++ b/xen/arch/x86/apic.c
> @@ -1051,64 +1051,32 @@ static void setup_APIC_timer(void)
>      local_irq_restore(flags);
>  }
>  
> -#define DEADLINE_MODEL_MATCH(m, fr) \
> -    { .vendor = X86_VENDOR_INTEL, .family = 6, .model = (m), \
> -      .feature = X86_FEATURE_TSC_DEADLINE, \
> -      .driver_data = (void *)(unsigned long)(fr) }
> +static const struct x86_cpu_id __initconst deadline_match[] = {
> +    X86_MATCH_VFMS(INTEL_HASWELL_X,   0x2, 0x3a), /* EP */
> +    X86_MATCH_VFMS(INTEL_HASWELL_X,   0x4, 0x0f), /* EX */
>  
> -static unsigned int __init hsx_deadline_rev(void)
> -{
> -    switch ( boot_cpu_data.x86_mask )
> -    {
> -    case 0x02: return 0x3a; /* EP */
> -    case 0x04: return 0x0f; /* EX */
> -    }
> +    X86_MATCH_VFM (INTEL_BROADWELL_X,      0x0b000020),
>  
> -    return ~0U;
> -}
> +    X86_MATCH_VFMS(INTEL_BROADWELL_D, 0x2, 0x00000011),
> +    X86_MATCH_VFMS(INTEL_BROADWELL_D, 0x3, 0x0700000e),
> +    X86_MATCH_VFMS(INTEL_BROADWELL_D, 0x4, 0x0f00000c),
> +    X86_MATCH_VFMS(INTEL_BROADWELL_D, 0x5, 0x0e000003),

Hmm, actually - why are Broadwell and ...

> -static unsigned int __init bdx_deadline_rev(void)
> -{
> -    switch ( boot_cpu_data.x86_mask )
> -    {
> -    case 0x02: return 0x00000011;
> -    case 0x03: return 0x0700000e;
> -    case 0x04: return 0x0f00000c;
> -    case 0x05: return 0x0e000003;
> -    }
> +    X86_MATCH_VFMS(INTEL_SKYLAKE_X,   0x3, 0x01000136),
> +    X86_MATCH_VFMS(INTEL_SKYLAKE_X,   0x4, 0x02000014),

... Skylake each split ...

> -    return ~0U;
> -}
> +    X86_MATCH_VFM (INTEL_HASWELL,          0x22),
> +    X86_MATCH_VFM (INTEL_HASWELL_L,        0x20),
> +    X86_MATCH_VFM (INTEL_HASWELL_G,        0x17),
>  
> -static unsigned int __init skx_deadline_rev(void)
> -{
> -    switch ( boot_cpu_data.x86_mask )
> -    {
> -    case 0x00 ... 0x02: return ~0U;
> -    case 0x03: return 0x01000136;
> -    case 0x04: return 0x02000014;
> -    }
> -
> -    return 0;
> -}
> -
> -static const struct x86_cpu_id __initconstrel deadline_match[] = {
> -    DEADLINE_MODEL_MATCH(0x3c, 0x22),             /* Haswell */
> -    DEADLINE_MODEL_MATCH(0x3f, hsx_deadline_rev), /* Haswell EP/EX */
> -    DEADLINE_MODEL_MATCH(0x45, 0x20),             /* Haswell D */
> -    DEADLINE_MODEL_MATCH(0x46, 0x17),             /* Haswell H */
> +    X86_MATCH_VFM (INTEL_BROADWELL,        0x25),
> +    X86_MATCH_VFM (INTEL_BROADWELL_G,      0x17),

... into disjoint groups (continuing ...

> -    DEADLINE_MODEL_MATCH(0x3d, 0x25),             /* Broadwell */
> -    DEADLINE_MODEL_MATCH(0x47, 0x17),             /* Broadwell H */
> -    DEADLINE_MODEL_MATCH(0x4f, 0x0b000020),       /* Broadwell EP/EX */
> -    DEADLINE_MODEL_MATCH(0x56, bdx_deadline_rev), /* Broadwell D */
> +    X86_MATCH_VFM (INTEL_SKYLAKE_L,        0xb2),
> +    X86_MATCH_VFM (INTEL_SKYLAKE,          0xb2),

... here)? The patch already isn't overly straightforward to review without
that.

Jan


  parent reply	other threads:[~2025-07-17  8:31 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16 17:31 [PATCH 0/6] x86: Convert x86_cpu_id to VFM Andrew Cooper
2025-07-16 17:31 ` [PATCH 1/6] x86: Sort headers Andrew Cooper
2025-07-17  7:10   ` Jan Beulich
2025-07-16 17:31 ` [PATCH 2/6] x86: Break struct x86_cpu_id out of processor.h Andrew Cooper
2025-07-17  7:23   ` Jan Beulich
2025-07-17 17:33     ` Andrew Cooper
2025-07-16 17:31 ` [PATCH 3/6] x86/match-cpu: Introduce X86_MATCH_VFM() and convert intel_idle_ids[] Andrew Cooper
2025-07-17  7:35   ` Jan Beulich
2025-07-17 17:39     ` Andrew Cooper
2025-07-18  5:38       ` Jan Beulich
2025-07-16 17:31 ` [PATCH 4/6] x86: Convert users of INTEL_FAM6_MODEL() to X86_MATCH_VFM() Andrew Cooper
2025-07-17  7:44   ` Jan Beulich
2025-07-17 17:57     ` Andrew Cooper
2025-07-18  5:40       ` Jan Beulich
2025-07-16 17:31 ` [PATCH 5/6] x86/match-cpu: Support matching on steppings Andrew Cooper
2025-07-17  8:11   ` Jan Beulich
2025-07-17 19:39     ` Andrew Cooper
2025-07-18  5:53       ` Jan Beulich
2025-07-18 10:29         ` Andrew Cooper
2025-07-18 13:28           ` Jan Beulich
2025-07-18 13:48             ` Andrew Cooper
2025-07-16 17:31 ` [PATCH 6/6] x86/apic: Convert the TSC deadline errata table to X86_MATCH_*() Andrew Cooper
2025-07-17  8:26   ` Jan Beulich
2025-07-17  9:02     ` Andrew Cooper
2025-07-17  9:33       ` Jan Beulich
2025-07-17 19:40         ` Andrew Cooper
2025-07-17  8:31   ` Jan Beulich [this message]
2025-07-17 19:45     ` Andrew Cooper
2025-07-18 10:07   ` [PATCH v1.1 " Andrew Cooper
2025-07-18 10:19     ` Jan Beulich
2025-07-18 10:23       ` Andrew Cooper
2025-07-18 10:55         ` Andrew Cooper
2025-07-18 14:06           ` Jan Beulich
2025-07-18 14:10             ` Andrew Cooper
2025-07-18 14:15         ` 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=3e3df60f-be4f-451c-aeb9-12a8d490cdc2@suse.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=roger.pau@citrix.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.