From: Jan Beulich <jbeulich@suse.com>
To: Simon Gaiser <simon@invisiblethingslab.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>, "Wei Liu" <wl@xen.org>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 2/4] x86/idle: Get PC{8..10} counters for Tiger and Alder Lake
Date: Tue, 18 Jul 2023 15:35:09 +0200 [thread overview]
Message-ID: <aa23a090-1883-008b-e395-2a3bca709258@suse.com> (raw)
In-Reply-To: <20230718132334.2087-1-simon@invisiblethingslab.com>
On 18.07.2023 15:23, Simon Gaiser wrote:
> ---
> xen/arch/x86/acpi/cpu_idle.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
This lacks both S-o-b and a proper description. The latter in
particular because you ...
> --- a/xen/arch/x86/acpi/cpu_idle.c
> +++ b/xen/arch/x86/acpi/cpu_idle.c
> @@ -155,6 +155,12 @@ static void cf_check do_get_hw_residencies(void *arg)
>
> switch ( c->x86_model )
> {
> + /* Tiger Lake */
> + case 0x8C:
> + case 0x8D:
> + /* Alder Lake */
> + case 0x97:
> + case 0x9A:
> /* 4th generation Intel Core (Haswell) */
> case 0x45:
> GET_PC8_RES(hw_res->pc8);
> @@ -185,9 +191,6 @@ static void cf_check do_get_hw_residencies(void *arg)
> case 0x6C:
> case 0x7D:
> case 0x7E:
> - /* Tiger Lake */
> - case 0x8C:
> - case 0x8D:
> /* Kaby Lake */
> case 0x8E:
> case 0x9E:
... don't just add new case labels, but you actually move two. It
wants explaining whether this was outright wrong, or what else
causes the movement.
Jan
next prev parent reply other threads:[~2023-07-18 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 13:23 [PATCH 2/4] x86/idle: Get PC{8..10} counters for Tiger and Alder Lake Simon Gaiser
2023-07-18 13:29 ` Simon Gaiser
2023-07-18 13:35 ` Jan Beulich [this message]
2023-07-18 13:46 ` Simon Gaiser
2023-07-18 14:04 ` Jan Beulich
2023-07-18 20:17 ` Simon Gaiser
2023-07-19 7:53 ` 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=aa23a090-1883-008b-e395-2a3bca709258@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=marmarek@invisiblethingslab.com \
--cc=roger.pau@citrix.com \
--cc=simon@invisiblethingslab.com \
--cc=wl@xen.org \
--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.