[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 5/8] x86: rename ARAT feature flag
- To: Jan Beulich <jbeulich@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
- Date: Tue, 18 Nov 2025 16:38:11 +0000
- 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=arcselector10001; 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=+LzYLrMVTikP/lipnUx0Clcv3W1fH3EHtSQ9Sjmu3uo=; b=kPzt7J8FD2TaefgXa/PvvEK1OnUfIi/JDB6MFYnVZA/z3ZxZhFwt8ArgxpMtlBSycFB/+O1Y/DowMzRe+vggu87xMaLSuUxS3QUvRWjfBkJJq1Tz1bESOKfbIoZLuMyt1nVk3jiZdKxe6liPJGQ7OlFj4wd7OhXto234iagbAfoXlR4QytN969wbWC55tsMLkSFso3E+0uxmv6QUxBiaQ+G7Bw6BUv81DzQXgdCV0HWwVr5B1jfT3pvw1voxn98A15HZ1x8ZFP53TMOmblSFQrWGDidylnXQ6jlraRxHVjYhnYYvqnvqLiYqfONsb4m/iTgAw69qc/CLB5HR7UVv2w==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=HvLtdhn1JpEu+SFe5+d8JFwWkeFXRAfeh1awrROCRvQvJulk0YkdvE6ou4WU59U41HrwctWEO22Gw5c5DE5oU3e6Fe3ZjpQ5kZ4Ki3PVCSfyOEXMGfKKgow69KeYOdOCQNnzPeKVB4ZOo4wZF2dsaqSwOIEizZpgeINAW9huReVNpIUii2G29D8x+w4ygJl2YsAJFaEdBTE4VZcLJ73M+nySgQsuZ50o63vI24UihpwGTWwBmM7dvcHUdRFhY82lFFsEFdH7LvJcZvMdqA0g/uBiL85DFH2dc0CFqv5o4McKpF6kgWI+bIF3xkxljpD9AdpPvIPv/HrB8WNqxaQ+Yw==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=citrix.com;
- Cc: Roger Pau Monné <roger.pau@xxxxxxxxxx>
- Delivery-date: Tue, 18 Nov 2025 16:38:28 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 18/11/2025 3:07 pm, Jan Beulich wrote:
> Add a XEN infix, to properly distinguish it from the CPUID feature flag
> (leaf 6 EAX bit 2).
>
> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
> ---
> Question is whether we still need opt_arat (and the command line option),
> or whether we could go directly from the CPUID bit (overriding it to on
> for older AMD [and Hygon?] CPUs). Or whether to have opt_arat affect the
> (host) CPU policy directly.
I have no particular love for opt_arat. I added it when there was no
way to force a system to fall back to an older timer.
As long as we've got some way of configuring the exact timer to, I'm not
fussed about keeping the top level boolean.
~Andrew
|
