[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wh9sDpbCPCekRr-fgWYz=9xa0_BOkEa+5vOr9Co-fNhrQ@mail.gmail.com>
Date: Mon, 17 Jul 2023 17:19:33 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: LKML <linux-kernel@...r.kernel.org>, x86@...nel.org,
Andrew Cooper <andrew.cooper3@...rix.com>,
Tom Lendacky <thomas.lendacky@....com>,
Paolo Bonzini <pbonzini@...hat.com>,
Wei Liu <wei.liu@...nel.org>,
Arjan van de Ven <arjan@...ux.intel.com>,
Juergen Gross <jgross@...e.com>
Subject: Re: [patch 41/58] x86/apic: Add max_apic_id member
So all of your patches make sense to me, but the whole apic_flat case
confuses me.
On Mon, 17 Jul 2023 at 16:15, Thomas Gleixner <tglx@...utronix.de> wrote:
>
> --- a/arch/x86/kernel/apic/apic_flat_64.c
> +++ b/arch/x86/kernel/apic/apic_flat_64.c
> @@ -94,6 +94,7 @@ static struct apic apic_flat __ro_after_
> .cpu_present_to_apicid = default_cpu_present_to_apicid,
> .phys_pkg_id = flat_phys_pkg_id,
>
> + .max_apic_id = 0xFE,
> .get_apic_id = flat_get_apic_id,
> .set_apic_id = set_apic_id,
flat_send_IPI_mask() can only deal with a single word mask. How the
heck can the max apic ID be more than 64?
I'm probably very confused.
Which is what the APIC code would do to anybody, which is why I'm
cheering your patch series on despite (or maybe _because_) it confuses
me.
Linus
Powered by blists - more mailing lists