From: "Morten Brørup" <mb@smartsharesystems.com>
To: "David Marchand" <david.marchand@redhat.com>,
"Bruce Richardson" <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>
Subject: RE: [RFC PATCH 3/3] build: deprecate HPET build option
Date: Tue, 2 Jun 2026 14:41:56 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F658DA@smartserver.smartshare.dk> (raw)
In-Reply-To: <CAJFAV8x5_JihAXe_bruriVu01b5wmF4fJ7vD42yFfNwpJQwDtQ@mail.gmail.com>
> On the other hand, did you consider dropping HPET altogether?
Google AI says that - on modern CPUs - the HPET has no advantages over the TSC.
This supports David's idea.
Suggestion:
Rewrite HPET APIs as a shim to TSC, and deprecate the HPET APIs.
-Morten
next prev parent reply other threads:[~2026-06-02 12:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 9:08 [RFC PATCH 0/3] remove unneeded build options Bruce Richardson
2026-06-02 9:08 ` [RFC PATCH 1/3] build: deprecate kernel dir option Bruce Richardson
2026-06-02 9:24 ` Morten Brørup
2026-06-02 9:08 ` [RFC PATCH 2/3] build: deprecate standalone tests option Bruce Richardson
2026-06-02 9:26 ` Morten Brørup
2026-06-02 9:08 ` [RFC PATCH 3/3] build: deprecate HPET build option Bruce Richardson
2026-06-02 10:47 ` Morten Brørup
2026-06-02 11:39 ` David Marchand
2026-06-02 12:37 ` Bruce Richardson
2026-06-02 12:41 ` Morten Brørup [this message]
2026-06-02 12:27 ` Bruce Richardson
2026-11-04 20:15 ` [PATCH v2 0/3] deprecate unneeded build options/support Bruce Richardson
2026-11-04 20:15 ` [PATCH v2 1/3] build: deprecate kernel dir option Bruce Richardson
2026-11-04 20:15 ` [PATCH v2 2/3] build: deprecate standalone tests option Bruce Richardson
2026-11-04 20:15 ` [PATCH v2 3/3] build: deprecate HPET support Bruce Richardson
2026-11-13 16:55 ` [PATCH v2 0/3] deprecate unneeded build options/support Bruce Richardson
2026-11-13 18:47 ` Stephen Hemminger
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=98CBD80474FA8B44BF855DF32C47DC35F658DA@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--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.