DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Konstantin Ananyev <konstantin.ananyev@huawei.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	 "wathsala.vithanage@arm.com" <wathsala.vithanage@arm.com>
Subject: Re: [PATCH v2] eal/x86: cache queried CPU flags
Date: Mon, 14 Oct 2024 20:29:43 +0200	[thread overview]
Message-ID: <CAJFAV8zhgKo-+y8hevE90Z-Sux0EmS=1=_eNgVXLxU1q53Npuw@mail.gmail.com> (raw)
In-Reply-To: <b629211f40ca44c7a30379fb115f15f7@huawei.com>

On Fri, Oct 11, 2024 at 3:37 PM Konstantin Ananyev
<konstantin.ananyev@huawei.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.
> >
> > Bugzilla ID: 1501
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> Acked-by: Konstantin Ananyev <konstantin.ananyev@huawei.com>

Applied, thanks Bruce.


-- 
David Marchand


      reply	other threads:[~2024-10-14 18:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-07 11:06 [PATCH] " Bruce Richardson
2024-10-07 11:23 ` David Marchand
2024-10-07 14:47   ` Wathsala Wathawana Vithanage
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 [this message]

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='CAJFAV8zhgKo-+y8hevE90Z-Sux0EmS=1=_eNgVXLxU1q53Npuw@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@huawei.com \
    --cc=wathsala.vithanage@arm.com \
    /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).