[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [XEN PATCH] x86/ACPI: Ignore entries with invalid APIC IDs when parsing MADT
- To: Jan Beulich <jbeulich@xxxxxxxx>
- From: Roger Pau Monné <roger.pau@xxxxxxxxxx>
- Date: Wed, 23 Aug 2023 11:13:56 +0200
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.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=kobuQxGY/jhkcbYwpQ8DfphLWkB4zKrJTYceNw4LwDE=; b=AbkYRes52DQ76Q1CvNJLF4h4pAxrGp8593KudgJKGtqhRAX/p+aPTcH3lukg3zLNTEQpvxMW8zbdYhMLXm9epfZ85vUFJL7YO9fN+d4hJ0rdij24ZrmIQtlg9gxiso9XXilh5B709VCkmFx6WMAhcTNICrH2wcwx9JP0wcI1H6Gz++PID/fk2XMP8WvL/RSdJpYSIi9fBh/iNHyU2Q77M/8PADESlp0mSYu3W3kdO4lo0smSHeltugzdgMkRqJuXv1QKCUykCraJDue9ZK15siTn9+6MGOy2r9Qiv4SmAsEQBMXgTkwoQxle6ZL3i1910At6HIpgr6eg710aBc/J4g==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=H6sqK6K5lsi5jp1A+kuALp5hCdrkkzx+uxgn1rizM+5rJnxiFoch+3PqLVxU4fNdzQ8h4+DiItIHQ0wThRSg0iw3hFsO1udh+h9j5s3z3+pJW+lE1Nid+4g8Q1ZAgOLHKAtv5J8HDUnLtX6d47ct+w8xXryIbTMmJccvE4gxVRw06vuwqaG5GQgt8qMvDgeApDhEc8DXAK2lqRWSK+C1cKfuZ/TOD6Za6OqCKhaha9JiuVXuq9iVlqh38hN+TCP5EYReSst5OWDUGMv1+FaxjNVe3Vvg9CeRrffmMbe43y9RyGWw84s1LhJ54p/uNIWVvTXrl9FpPWpsXmrE031SsQ==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=citrix.com;
- Cc: Simon Gaiser <simon@xxxxxxxxxxxxxxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Wei Liu <wl@xxxxxxx>, Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
- Delivery-date: Wed, 23 Aug 2023 09:14:23 +0000
- Ironport-data: A9a23:Wg8jGa3zcF/0h8fCrPbD5TRwkn2cJEfYwER7XKvMYLTBsI5bpzAFy 2sdW2qEaKmOYjH2KN1zOo6z8hgFvJ7QzoRjTAQ4pC1hF35El5HIVI+TRqvS04F+DeWYFR46s J9OAjXkBJppJpMJjk71atANlVEliefTAOK6ULWeUsxIbVcMYD87jh5+kPIOjIdtgNyoayuAo tq3qMDEULOf82cc3lk8teTb8XuDgNyo4GlD5gxkPqgS1LPjvyJ94Kw3dPnZw0TQGuG4LsbiL 87fwbew+H/u/htFIrtJRZ6iLyXm6paLVeS/oiI+t5qK23CulQRrukoPD9IOaF8/ttm8t4sZJ OOhF3CHYVxB0qXkwIzxWvTDes10FfUuFLTveRBTvSEPpqFvnrSFL/hGVSkL0YMkFulfUT9A2 NgqNiw3YxWahvKWh6m0Vct1r5F2RCXrFNt3VnBI6xj8VK9jareaBqLA6JlfwSs6gd1IEbDGf c0FZDFzbRPGJRpSJlMQD5F4l+Ct7pX9W2QA9BTJ+uxqvS6Kk1QZPLvFabI5fvSQQspYhACAr 3/u9GXlGBAKcteYzFJp91r1376RxnumBth6+LuQ+eFGuwXUwEspUjI2Fl+WvtKYhki9cocKQ 6AT0m90xUQoz2SpRNTgWxyzoFafowURHdFXFoUS8wCIzaz84gCHB3MFRDpMdNwnssAtQTUgk FSOmrvBGjhHoLCTD3WH+d+8qDqoPCEPIGwqZCkaTBAE6d3uvIEyiB3USt9pVqWyi7XdCTz2h jyHsiU6r7ESltIQkbW2+0jdhDChrYSPSRQ6jjg7RUqg5wJ9IYWiPoqh7AGC6e4addnBCF6co HIDhs6SqvgUCo2AnzCMR+NLG6y14/GCM3vXhlsH84QdyglBMkWLJeh4iAyS7m81WirYUVcFu HPuhD4=
- Ironport-hdrordr: A9a23:JVkPl6yUBNB0soOSv0poKrPw2r1zdoMgy1knxilNoHxuH/BwWf rPoB17726TtN91YhsdcL+7V5VoLUmzyXcx2/hyAV7AZniAhILLFvAA0WKK+VSJdxEWtNQtsJ uIG5IUNDSaNykfsS+V2miF+9ZL+qj5zEir792usUuEm2tRGtBdBwQSMHfqLqVvLjM2fKbQjP Cnl7d6TzzLQwVuUu2LQkMrcsLkvNPxmJfvcXc9dmIaAFnnt0LS1FbieSLopCsjbw==
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On Mon, Aug 07, 2023 at 03:17:18PM +0200, Jan Beulich wrote:
> On 07.08.2023 14:55, Simon Gaiser wrote:
> > Jan Beulich:
> >> On 07.08.2023 11:38, Simon Gaiser wrote:
> >>> It seems some firmwares put dummy entries in the ACPI MADT table for non
> >>> existing processors. On my NUC11TNHi5 those have the invalid APIC ID
> >>> 0xff. Linux already has code to handle those cases both in
> >>> acpi_parse_lapic [1] as well as in acpi_parse_x2apic [2]. So add the
> >>> same check to Xen.
> >>
> >> I'm afraid it doesn't become clear to me what problem you're trying to
> >> solve.
> >
> > I want Xen to not think there are possible CPUs that actually never can
> > be there.
>
> Did you try using "maxcpus=" on the command line? If that doesn't work
> well enough (perhaps because of causing undesirable log messages), maybe
> we need some way to say "no CPU hotplug" on the command line.
A Kconfig option to disable CPU hotplug at build time would also be
interesting IMO.
Thanks, Roger.
|
