patches for DPDK stable branches
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev <dev@dpdk.org>, dpdk stable <stable@dpdk.org>,
	 Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-stable] [PATCH] eal/x86: fix some CPU extended features
Date: Fri, 8 Oct 2021 13:08:54 +0200	[thread overview]
Message-ID: <CAJFAV8zW3vY8GsCa6OqEAdQ87C-Y6i=kB9Qdhv01_3L6WpURHA@mail.gmail.com> (raw)
In-Reply-To: <YWAaQGj4pEJmLh9R@bricha3-MOBL.ger.corp.intel.com>

On Fri, Oct 8, 2021 at 12:15 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> On Wed, Oct 06, 2021 at 09:20:08PM +0200, David Marchand wrote:
> > Caught while checking CPUID related stuff in OVS.
> >
> > According to [1], for Structured Extended Feature Flags Enumeration Leaf
> > (EAX = 0x07H, ECX = 0):
> >
> > - BMI1 is associated to EBX, bit 3 (was incorrectly 2),
> > - SMEP is associated to EBX, bit 7 (was incorrectly 6),
> > - BMI2 is associated to EBX, bit 8 (was incorrectly 7),
> > - ERMS is associated to EBX, bit 9 (was incorrectly 8),
> >
> > This patch then sorts the rest of the extended features (leaf 0) for
> > readability.
> >
> > 1: https://software.intel.com/sites/default/files/managed/c5/15/architecture-instruction-set-extensions-programming-reference.pdf
> >
> > Fixes: af75078fece3 ("first public release")
>
> Wow, I'm surprised at it being incorrect this long, but checking the
> original commit of code, it does indeed seem true that this is the correct
> fixes line!
>
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
>
> Ideally, I think the fixes should go in a separate patch from the
> reordering, but I don't feel strongly about it so this is ok as either one
> or two patches IMHO.

I was reading the datasheet and comparing the defines one by one, so
easier with sorted defines.
Now that I identified the wrong entries, I am fine with splitting
since it eases backport on 19.11.

I'll send v2 with your ack on both.


-- 
David Marchand


  reply	other threads:[~2021-10-08 11:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06 19:20 David Marchand
2021-10-08 10:15 ` Bruce Richardson
2021-10-08 11:08   ` David Marchand [this message]
2021-10-08 12:07 ` [dpdk-stable] [PATCH v2 1/2] eal/x86: fix some CPU extended features definitions David Marchand
2021-10-12 19:06   ` 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='CAJFAV8zW3vY8GsCa6OqEAdQ87C-Y6i=kB9Qdhv01_3L6WpURHA@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=stable@dpdk.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 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).