From: Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com>
To: David Marchand <david.marchand@redhat.com>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Min Zhou <zhoumin@loongson.cn>,
David Christensen <drc@linux.ibm.com>,
Stanislaw Kardach <stanislaw.kardach@gmail.com>,
Konstantin Ananyev <konstantin.ananyev@huawei.com>,
nd <nd@arm.com>
Subject: RE: [PATCH] eal/x86: cache queried CPU flags
Date: Mon, 7 Oct 2024 14:47:33 +0000 [thread overview]
Message-ID: <PAWPR08MB8909F61F71DF9A149DB7C7C49F7D2@PAWPR08MB8909.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8xX9HSvKzD_kufhz-qa7ssYBCEQ+MQnPvKDh3n5ivwhSg@mail.gmail.com>
> On Mon, Oct 7, 2024 at 1:07 PM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> >
> > Rather than re-querying the HW each time a CPU flag is requested, we
> > can just save the return value in the flags array. This should speed
> > up repeated querying of CPU flags, and provides a workaround for a
> > reported issue where errors are seen with constant querying of the
> > AVX-512 CPU flag from a non-AVX VM.
>
> This could be applied to other arches cpuflag implementation.
> Copying other arches maintainers as a fyi.
>
+1
next prev parent reply other threads:[~2024-10-07 14:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 11:06 Bruce Richardson
2024-10-07 11:23 ` David Marchand
2024-10-07 14:47 ` Wathsala Wathawana Vithanage [this message]
2024-10-07 16:29 ` Wathsala Wathawana Vithanage
2024-10-07 16:43 ` Bruce Richardson
2024-10-07 17:30 ` Wathsala Wathawana Vithanage
2024-10-11 12:42 ` Konstantin Ananyev
2024-10-11 12:48 ` Bruce Richardson
2024-10-11 13:00 ` Konstantin Ananyev
2024-10-11 13:31 ` Bruce Richardson
2024-10-11 13:33 ` [PATCH v2] " Bruce Richardson
2024-10-11 13:37 ` Konstantin Ananyev
2024-10-14 18:29 ` David Marchand
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=PAWPR08MB8909F61F71DF9A149DB7C7C49F7D2@PAWPR08MB8909.eurprd08.prod.outlook.com \
--to=wathsala.vithanage@arm.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=drc@linux.ibm.com \
--cc=konstantin.ananyev@huawei.com \
--cc=nd@arm.com \
--cc=stanislaw.kardach@gmail.com \
--cc=zhoumin@loongson.cn \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).