From: Jakub Kicinski <kuba@kernel.org>
To: "Olech, Milena" <milena.olech@intel.com>
Cc: "Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"Dumazet, Eric" <edumazet@google.com>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
"Kolacinski, Karol" <karol.kolacinski@intel.com>,
"richardcochran@gmail.com" <richardcochran@gmail.com>,
"Lobakin, Aleksander" <aleksander.lobakin@intel.com>,
Willem de Bruijn <willemb@google.com>,
"Mina Almasry" <almasrymina@google.com>,
"Salin, Samuel" <samuel.salin@intel.com>
Subject: Re: [PATCH net-next 04/10] idpf: negotiate PTP capabilities and get PTP clock
Date: Wed, 2 Apr 2025 09:37:31 -0700 [thread overview]
Message-ID: <20250402093731.1230cff9@kernel.org> (raw)
In-Reply-To: <MW4PR11MB588909DAED47807C491FE7C38EAF2@MW4PR11MB5889.namprd11.prod.outlook.com>
On Wed, 2 Apr 2025 15:23:53 +0000 Olech, Milena wrote:
> >So hi is latched when lo is read? Or the timer may wrap between
> >the reads? Can reads happen in parallel (re-latching hi)?
>
> Actually we have HW support to latch both values simultaneously.
>
> Hi and Lo are latched in idpf_ptp_enable_shtime function, so I will move
> lo right after ptp_read_system_postts.
You may need a lock, too, with two concurrent readers one can "re-latch"
the value for the other?
next prev parent reply other threads:[~2025-04-02 16:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 16:13 [PATCH net-next 00/10][pull request] idpf: add initial PTP support Tony Nguyen
2025-03-18 16:13 ` [PATCH net-next 01/10] " Tony Nguyen
2025-03-25 12:44 ` Jakub Kicinski
2025-03-25 21:05 ` Jacob Keller
2025-04-02 13:16 ` Olech, Milena
2025-03-18 16:13 ` [PATCH net-next 02/10] virtchnl: add PTP virtchnl definitions Tony Nguyen
2025-03-18 16:13 ` [PATCH net-next 03/10] idpf: move virtchnl structures to the header file Tony Nguyen
2025-03-18 16:13 ` [PATCH net-next 04/10] idpf: negotiate PTP capabilities and get PTP clock Tony Nguyen
2025-03-25 12:49 ` Jakub Kicinski
2025-03-25 21:07 ` Jacob Keller
2025-03-26 8:24 ` Przemek Kitszel
2025-04-02 15:23 ` Olech, Milena
2025-04-02 16:37 ` Jakub Kicinski [this message]
2025-03-18 16:13 ` [PATCH net-next 05/10] idpf: add mailbox access to read PTP clock time Tony Nguyen
2025-03-18 16:13 ` [PATCH net-next 06/10] idpf: add PTP clock configuration Tony Nguyen
2025-03-18 16:13 ` [PATCH net-next 07/10] idpf: add Tx timestamp capabilities negotiation Tony Nguyen
2025-03-18 16:13 ` [PATCH net-next 08/10] idpf: add Tx timestamp flows Tony Nguyen
2025-03-25 13:00 ` Jakub Kicinski
2025-03-25 21:10 ` Jacob Keller
2025-04-02 14:57 ` Olech, Milena
2025-03-18 16:13 ` [PATCH net-next 09/10] idpf: add support for Rx timestamping Tony Nguyen
2025-03-18 16:13 ` [PATCH net-next 10/10] idpf: change the method for mailbox workqueue allocation Tony Nguyen
2025-03-25 21:08 ` Jacob Keller
2025-04-02 13:22 ` Olech, Milena
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=20250402093731.1230cff9@kernel.org \
--to=kuba@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=karol.kolacinski@intel.com \
--cc=milena.olech@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=richardcochran@gmail.com \
--cc=samuel.salin@intel.com \
--cc=willemb@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;
as well as URLs for NNTP newsgroup(s).