The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jacob Keller <jacob.e.keller@intel.com>
To: Harshitha Ramamurthy <hramamurthy@google.com>, <netdev@vger.kernel.org>
Cc: <joshwash@google.com>, <andrew+netdev@lunn.ch>,
	<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
	<pabeni@redhat.com>, <richardcochran@gmail.com>,
	<jstultz@google.com>, <tglx@kernel.org>, <sboyd@kernel.org>,
	<willemb@google.com>, <nktgrg@google.com>, <jfraker@google.com>,
	<ziweixiao@google.com>, <maolson@google.com>,
	<jordanrhee@google.com>, <thostet@google.com>,
	<alok.a.tiwari@oracle.com>, <pkaligineedi@google.com>,
	<horms@kernel.org>, <dwmw2@infradead.org>, <yyd@google.com>,
	<jefrogers@google.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v6 2/3] gve: make nic clock reads thread safe
Date: Thu, 7 May 2026 14:15:57 -0700	[thread overview]
Message-ID: <547d6394-5c46-4a3d-9166-2d1f24c51932@intel.com> (raw)
In-Reply-To: <20260507211304.3046526-3-hramamurthy@google.com>

On 5/7/2026 2:13 PM, Harshitha Ramamurthy wrote:
> From: Ankit Garg <nktgrg@google.com>
> 
> Add a mutex to protect the shared DMA buffer that receives NIC
> timestamp reports. The NIC timestamp will be read from two different
> threads: the periodic worker and upcoming `gettimex64`.
> 
> Move clock registration to the last step of initialization to ensure
> that all data needed by the clock module is initialized before
> the clock is exposed to usermode.
> 
> Reviewed-by: Joshua Washington <joshwash@google.com>
> Signed-off-by: Ankit Garg <nktgrg@google.com>
> Signed-off-by: Jordan Rhee <jordanrhee@google.com>
> Signed-off-by: Harshitha Ramamurthy <hramamurthy@google.com>
> ---
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>

  reply	other threads:[~2026-05-07 21:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07 21:13 [PATCH net-next v6 0/3] gve: add support for PTP gettimex64 Harshitha Ramamurthy
2026-05-07 21:13 ` [PATCH net-next v6 1/3] gve: skip error logging for retryable AdminQ commands Harshitha Ramamurthy
2026-05-07 21:14   ` Jacob Keller
2026-05-10  4:31     ` Jordan Rhee
2026-05-07 21:13 ` [PATCH net-next v6 2/3] gve: make nic clock reads thread safe Harshitha Ramamurthy
2026-05-07 21:15   ` Jacob Keller [this message]
2026-05-07 21:13 ` [PATCH net-next v6 3/3] gve: implement PTP gettimex64 Harshitha Ramamurthy
2026-05-07 21:23   ` Jacob Keller
2026-05-08 17:43     ` Jordan Rhee
2026-05-08 21:53       ` Jacob Keller
2026-05-10  4:54   ` Jordan Rhee

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=547d6394-5c46-4a3d-9166-2d1f24c51932@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=alok.a.tiwari@oracle.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dwmw2@infradead.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=hramamurthy@google.com \
    --cc=jefrogers@google.com \
    --cc=jfraker@google.com \
    --cc=jordanrhee@google.com \
    --cc=joshwash@google.com \
    --cc=jstultz@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maolson@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=nktgrg@google.com \
    --cc=pabeni@redhat.com \
    --cc=pkaligineedi@google.com \
    --cc=richardcochran@gmail.com \
    --cc=sboyd@kernel.org \
    --cc=tglx@kernel.org \
    --cc=thostet@google.com \
    --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