From: Harshitha Ramamurthy <hramamurthy@google.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, jeroendb@google.com, hramamurthy@google.com,
andrew+netdev@lunn.ch, willemb@google.com, ziweixiao@google.com,
pkaligineedi@google.com, yyd@google.com, joshwash@google.com,
shailend@google.com, linux@treblig.org, thostet@google.com,
jfraker@google.com, richardcochran@gmail.com,
jdamato@fastly.com, vadim.fedorenko@linux.dev, horms@kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next v5 0/8] gve: Add Rx HW timestamping support
Date: Sat, 14 Jun 2025 00:07:46 +0000 [thread overview]
Message-ID: <20250614000754.164827-1-hramamurthy@google.com> (raw)
From: Ziwei Xiao <ziweixiao@google.com>
This patch series add the support of Rx HW timestamping, which sends
adminq commands periodically to the device for clock synchronization with
the NIC.
The ability to read the PHC from user space will be added in the
future patch series when adding the actual PTP support. For this patch
series, it's adding the initial ptp to utilize the ptp_schedule_worker
to schedule the work of syncing the NIC clock.
Changes:
v5:
- Change to register PTP when initializing the driver and keep it
alive until destroying the driver. (Jakub Kicinski)
- Utilize ptp_cancel_worker_sync instead of unregistering the PHC
every time when rx timestamping is disabled. (Jakub Kicinski)
- Add gve_clock_nic_ts_read before the ptp_schedule_worker to do
the first refresh. (Jakub Kicinski)
- Add the phc_index info into the gve_get_ts_info. (Jakub Kicinski)
v4:
- release the ptp in the error path of gve_init_clock (Jakub Kicinski)
- add two more reserved fields in gve_nic_ts_report, anticipating
upcoming use, to align size expectations with the device from the
start (team internal review, Shachar Raindel)
v3:
- change the last_read to be u64 on patch 6/8 (Vadim Fedorenko)
- update the title and commit message of patch 7/8 to show it's adding
support for ndo functions instead of ioctls (Jakub Kicinski)
- Utilize extack for error logging instead of dev_err (Jakub Kicinski)
v2:
- add initial PTP device support to utilize the ptp's aux_work to
schedule sending adminq commands periodically (Jakub Kicinski,
Vadim Fedorenko)
- add adminq lock patch into this patch series instead of sending out
to net since it's only needed to resolve the conflicts between the
upcoming PTP aux_work and the queue creation/destruction adminq
commands (Jakub Kicinski)
- add the missing READ_ONCE (Joe Damato)
Harshitha Ramamurthy (1):
gve: Add initial PTP device support
John Fraker (5):
gve: Add device option for nic clock synchronization
gve: Add adminq command to report nic timestamp
gve: Add rx hardware timestamp expansion
gve: Implement ndo_hwtstamp_get/set for RX timestamping
gve: Advertise support for rx hardware timestamping
Kevin Yang (1):
gve: Add support to query the nic clock
Ziwei Xiao (1):
gve: Add adminq lock for queues creation and destruction
drivers/net/ethernet/google/Kconfig | 1 +
drivers/net/ethernet/google/gve/Makefile | 4 +-
drivers/net/ethernet/google/gve/gve.h | 35 +++++
drivers/net/ethernet/google/gve/gve_adminq.c | 98 ++++++++++--
drivers/net/ethernet/google/gve/gve_adminq.h | 28 ++++
.../net/ethernet/google/gve/gve_desc_dqo.h | 3 +-
drivers/net/ethernet/google/gve/gve_ethtool.c | 26 +++-
drivers/net/ethernet/google/gve/gve_main.c | 53 ++++++-
drivers/net/ethernet/google/gve/gve_ptp.c | 139 ++++++++++++++++++
drivers/net/ethernet/google/gve/gve_rx_dqo.c | 26 ++++
10 files changed, 396 insertions(+), 17 deletions(-)
create mode 100644 drivers/net/ethernet/google/gve/gve_ptp.c
--
2.50.0.rc1.591.g9c95f17f64-goog
next reply other threads:[~2025-06-14 0:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 0:07 Harshitha Ramamurthy [this message]
2025-06-14 0:07 ` [PATCH net-next v5 1/8] gve: Add device option for nic clock synchronization Harshitha Ramamurthy
2025-06-14 0:07 ` [PATCH net-next v5 2/8] gve: Add adminq command to report nic timestamp Harshitha Ramamurthy
2025-06-14 0:07 ` [PATCH net-next v5 3/8] gve: Add initial PTP device support Harshitha Ramamurthy
2025-06-14 0:07 ` [PATCH net-next v5 4/8] gve: Add adminq lock for queues creation and destruction Harshitha Ramamurthy
2025-06-14 0:07 ` [PATCH net-next v5 5/8] gve: Add support to query the nic clock Harshitha Ramamurthy
2025-06-14 0:07 ` [PATCH net-next v5 6/8] gve: Add rx hardware timestamp expansion Harshitha Ramamurthy
2025-06-14 0:07 ` [PATCH net-next v5 7/8] gve: Implement ndo_hwtstamp_get/set for RX timestamping Harshitha Ramamurthy
2025-06-14 0:07 ` [PATCH net-next v5 8/8] gve: Advertise support for rx hardware timestamping Harshitha Ramamurthy
2025-06-16 22:30 ` [PATCH net-next v5 0/8] gve: Add Rx HW timestamping support patchwork-bot+netdevbpf
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=20250614000754.164827-1-hramamurthy@google.com \
--to=hramamurthy@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jdamato@fastly.com \
--cc=jeroendb@google.com \
--cc=jfraker@google.com \
--cc=joshwash@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=richardcochran@gmail.com \
--cc=shailend@google.com \
--cc=thostet@google.com \
--cc=vadim.fedorenko@linux.dev \
--cc=willemb@google.com \
--cc=yyd@google.com \
--cc=ziweixiao@google.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
all inboxes | Powered by JetHome®