dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Vyal <dmitryvyal-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Thomas Monjalon
	<thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: Sporadic errors while initializing NICs in example applications, dpdk-1.5.0r1
Date: Fri, 06 Dec 2013 16:43:11 +0400	[thread overview]
Message-ID: <52A1C65F.7000308@gmail.com> (raw)
In-Reply-To: <1535896.tMWsNx1bj7@x220>

On 11/29/2013 04:39 PM, Thomas Monjalon wrote:
> 29/11/2013 13:25, Thomas Monjalon :
>
> Please check that your hardware do not support invariant TSC.
> It would explain why you need to fix frequency.
>
> I attach a simple code to test CPU feature "Invariant TSC".

I compiled and ran the code on all the platforms I had troubles on. 
Invariant TSC is supported everywhere.

> It seems that the file is stripped on the mailing-list.
> Code inlined:
>
> #include <stdlib.h>
> #include <stdio.h>
> #include <unistd.h>
> #include <stdint.h>
>
>
> int main()
> {
>      uint32_t a = 0x80000000;
>      uint32_t b, d;
>
>      __asm__("cpuid;"
>              :"=a"(b)
>              :"0"(a));
>
>      if (b >= 0x80000007) {
>
>          a = 0x80000007;
>          __asm__("cpuid;"
>                  :"=a"(b), "=d"(d)
>                  :"0"(a));
>
>          if (d & (1<<8)) {
>              printf("Invariant TSC is supported\n");
>          } else{
>              printf("Invariant TSC is NOT supported\n");
>          }
>      } else {
>          printf("No support for Advanced Power Management Information in
> CPUID\n");
>      }
>      return 0;
> }
>

  reply	other threads:[~2013-12-06 12:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22 12:29 Sporadic errors while initializing NICs in example applications, dpdk-1.5.0r1 Dmitry Vyal
     [not found] ` <528F4E41.2000405-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-11-22 12:48   ` Thomas Monjalon
     [not found]     ` <201311221348.02307.thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-11-27 14:06       ` Dmitry Vyal
     [not found]         ` <5295FC76.70201-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-11-27 14:10           ` jigsaw
2013-11-27 14:42           ` Thomas Monjalon
     [not found]             ` <201311271542.05288.thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-11-28 11:01               ` Richardson, Bruce
     [not found]                 ` <59AF69C657FD0841A61C55336867B5B01A9781FC-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-11-29 10:53                   ` Dmitry Vyal
     [not found]                     ` <52987236.3020707-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-11-29 12:25                       ` Thomas Monjalon
2013-11-29 12:39                         ` Thomas Monjalon
2013-12-06 12:43                           ` Dmitry Vyal [this message]
2013-11-29 18:20                         ` 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=52A1C65F.7000308@gmail.com \
    --to=dmitryvyal-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.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).