All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/eventdev Bug 1626] HPET timers do not work on the Osage customer reference platform
Date: Mon, 03 Feb 2025 02:37:15 +0000	[thread overview]
Message-ID: <bug-1626-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1626

            Bug ID: 1626
           Summary: HPET timers do not work on the Osage customer
                    reference platform
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: eventdev
          Assignee: dev@dpdk.org
          Reporter: nandinipersad361@gmail.com
  Target Milestone: ---

HPET timers do not work on the Osage customer reference platform which includes
an Intel® Xeon® processor 5500 series processor) using the released BIOS from
Intel.

Implication:
On Osage boards, the implementation of the rte_delay_us() function must be
changed to not use the HPET timer.

Resolution/Workaround:
This can be addressed by building the system with RTE_LIBEAL_USE_HPET unset or
by using the --no-hpet EAL option.

Affected Environment/Platform:
The Osage customer reference platform. Other vendor platforms with Intel® Xeon®
processor 5500 series processors should work correctly, provided the BIOS
supports HPET.

Driver/Module:
lib/eal/include/rte_cycles.h

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3161 bytes --]

                 reply	other threads:[~2025-02-03  2:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-1626-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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 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.