DPDK patches and discussions
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: "H. Peter Anvin" <hpa@linux.intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] eal_common_cpuflags: Fix %rbx corruption, and simplify the code
Date: Fri, 21 Mar 2014 13:48:39 -0400	[thread overview]
Message-ID: <20140321174839.GB21998@hmsreliant.think-freely.org> (raw)
In-Reply-To: <532C54C6.2060202@linux.intel.com>

On Fri, Mar 21, 2014 at 08:03:34AM -0700, H. Peter Anvin wrote:
> On 03/21/2014 07:49 AM, Neil Horman wrote:
> > From: "H. Peter Anvin" <hpa@linux.intel.com>
> > 
> > Neil Horman reported that on x86-64 the upper half of %rbx would get
> > clobbered when the code was compiled PIC or PIE, because the
> > i386-specific code to preserve %ebx was incorrectly compiled.
> > 
> > However, the code is really way more complex than it needs to be.  For
> > one thing, the CPUID instruction only needs %eax (leaf) and %ecx
> > (subleaf) as parameters, and since we are testing for bits, we might
> > as well list the bits explicitly.  Furthermore, we can use an array
> > rather than doing a switch statement inside a structure.
> > 
> > Reported-by: Neil Horman <nhorman@tuxdriver.com>
> > Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
> > Tested-by: Neil Horman <nhorman@tuxdriver.com>
> > 
> 
> Thank you for dealing with this!
> 
> On the subject of my other email... are C99 initializers acceptable in
> dpdk?  If so, I think making that change, too, would be a good idea.
> 
I'll have to defer this to others, I'm not sure what the accepted initalization
method is.  I'm guessing their fine, as both icc and gcc allow them and those
are the supported compilers for dpdk, but I'd like to hear someone in the
maintainership comment.

Best
Neil

> 	-hpa
> 
> 
> 

  reply	other threads:[~2014-03-21 17:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1395330830-1310-1-git-send-email-hpa@linux.intel.com>
2014-03-20 16:39 ` [dpdk-dev] [RFC UNTESTED PATCH] " Neil Horman
2014-03-20 17:02   ` Thomas Monjalon
2014-03-20 18:04   ` Neil Horman
2014-03-21 14:49   ` [dpdk-dev] [PATCH v2] " Neil Horman
2014-03-21 15:03     ` H. Peter Anvin
2014-03-21 17:48       ` Neil Horman [this message]
2014-03-24 11:18         ` Thomas Monjalon
2014-03-24 17:44   ` [dpdk-dev] [PATCH v3] " Neil Horman
2014-03-24 18:09     ` H. Peter Anvin
2014-03-24 19:52       ` Neil Horman
2014-03-24 20:47         ` H. Peter Anvin
2014-03-25 10:41           ` Neil Horman
2014-03-25 17:03   ` [dpdk-dev] [PATCH v4] " Neil Horman
2014-03-25 17:06     ` Chris Wright
2014-03-25 17:37     ` H. Peter Anvin
2014-03-25 19:52   ` [dpdk-dev] [PATCH v5] " Neil Horman
2014-03-25 20:51     ` H. Peter Anvin
2014-04-02 11:16       ` Neil Horman
2014-04-02 11:53         ` Thomas Monjalon
2014-04-02 12:42       ` 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=20140321174839.GB21998@hmsreliant.think-freely.org \
    --to=nhorman@tuxdriver.com \
    --cc=dev@dpdk.org \
    --cc=hpa@linux.intel.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).