From: Jerin Jacob <jerinjacobk@gmail.com>
To: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Cc: Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
"Ruifeng Wang (Arm Technology China)" <Ruifeng.Wang@arm.com>,
Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1] eal/arm64: fix aarch64 reg platform value
Date: Thu, 22 Apr 2021 14:52:04 +0530 [thread overview]
Message-ID: <CALBAE1P_4owMiCVyLY+1zbyh2F2W_FCVnV64Jfm7ji7Gvq0W4A@mail.gmail.com> (raw)
In-Reply-To: <1619082711-7471-1-git-send-email-juraj.linkes@pantheon.tech>
On Thu, Apr 22, 2021 at 2:41 PM Juraj Linkeš <juraj.linkes@pantheon.tech> wrote:
>
> REG_PLATFORM only uses bit 0 to indicate whether the value retrieved
> from hardware matches PLATFORM_STR.
>
> Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
> Fixes: 97523f822ba9 ("eal/arm: add CPU flags for ARMv8")
Fixes and cc stable should go above Signoff.
> Cc: jerinj@marvell.com
> Cc: stable@dpdk.org
Reviewed-by: Jerin Jacob <jerinj@marvell.com>
> ---
> lib/eal/arm/rte_cpuflags.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/eal/arm/rte_cpuflags.c b/lib/eal/arm/rte_cpuflags.c
> index e3a53bcece..e709a2800e 100644
> --- a/lib/eal/arm/rte_cpuflags.c
> +++ b/lib/eal/arm/rte_cpuflags.c
> @@ -108,7 +108,7 @@ const struct feature_entry rte_cpu_feature_table[] = {
> FEAT_DEF(SVEF32MM, REG_HWCAP2, 10)
> FEAT_DEF(SVEF64MM, REG_HWCAP2, 11)
> FEAT_DEF(SVEBF16, REG_HWCAP2, 12)
> - FEAT_DEF(AARCH64, REG_PLATFORM, 1)
> + FEAT_DEF(AARCH64, REG_PLATFORM, 0)
> };
> #endif /* RTE_ARCH */
>
> --
> 2.20.1
>
next prev parent reply other threads:[~2021-04-22 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 9:11 [dpdk-dev] [PATCH v1] eal/arm64: fix aarch64 reg platform value Juraj Linkeš
2021-04-22 9:22 ` Jerin Jacob [this message]
2021-04-22 9:25 ` Ruifeng Wang
2021-05-04 16:41 ` Thomas Monjalon
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=CALBAE1P_4owMiCVyLY+1zbyh2F2W_FCVnV64Jfm7ji7Gvq0W4A@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=juraj.linkes@pantheon.tech \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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.