From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Chris H <christopher.s.hall@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Cc: <david.zage@intel.com>, <vinicius.gomes@intel.com>,
<netdev@vger.kernel.org>, <rodrigo.cadore@l-acoustics.com>,
<vinschen@redhat.com>
Subject: Re: [PATCH iwl-net v2 4/4] igc: Add lock preventing multiple simultaneous PTM transactions
Date: Tue, 29 Oct 2024 14:20:14 -0700 [thread overview]
Message-ID: <b22e920a-34c9-4926-9cf1-02dc24fcfb77@intel.com> (raw)
In-Reply-To: <20241023023040.111429-5-christopher.s.hall@intel.com>
On 10/22/2024 7:30 PM, Chris H wrote:
> From: Christopher S M Hall <christopher.s.hall@intel.com>
>
> Add a mutex around the PTM transaction to prevent multiple transactors
>
> Multiple processes try to initiate a PTM transaction, one or all may
> fail. This can be reproduced by running two instances of the
> following:
>
> $ sudo phc2sys -O 0 -i tsn0 -m
>
> PHC2SYS exits with:
>
> "ioctl PTP_OFFSET_PRECISE: Connection timed out" when the PTM transaction
> fails
>
> Note: Normally two instance of PHC2SYS will not run, but one process
> should not break another.
>
> Fixes: a90ec8483732 ("igc: Add support for PTP getcrosststamp()")
> Signed-off-by: Christopher S M Hall <christopher.s.hall@intel.com>
> ---
> drivers/net/ethernet/intel/igc/igc.h | 1 +
> drivers/net/ethernet/intel/igc/igc_ptp.c | 12 ++++++++++--
> 2 files changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/igc/igc.h b/drivers/net/ethernet/intel/igc/igc.h
> index eac0f966e0e4..323db1e2be38 100644
> --- a/drivers/net/ethernet/intel/igc/igc.h
> +++ b/drivers/net/ethernet/intel/igc/igc.h
> @@ -319,6 +319,7 @@ struct igc_adapter {
> struct timespec64 prev_ptp_time; /* Pre-reset PTP clock */
> ktime_t ptp_reset_start; /* Reset time in clock mono */
> struct system_time_snapshot snapshot;
> + struct mutex ptm_lock; /* Only allow one PTM transaction at a time */
>
> char fw_version[32];
>
> diff --git a/drivers/net/ethernet/intel/igc/igc_ptp.c b/drivers/net/ethernet/intel/igc/igc_ptp.c
> index fb885fcaa97c..4e1379b7d2ee 100644
> --- a/drivers/net/ethernet/intel/igc/igc_ptp.c
> +++ b/drivers/net/ethernet/intel/igc/igc_ptp.c
> @@ -1068,9 +1068,16 @@ static int igc_ptp_getcrosststamp(struct ptp_clock_info *ptp,
> {
> struct igc_adapter *adapter = container_of(ptp, struct igc_adapter,
> ptp_caps);
> + int ret;
>
> - return get_device_system_crosststamp(igc_phc_get_syncdevicetime,
> - adapter, &adapter->snapshot, cts);
> + /* This blocks until any in progress PTM transactions complete */
> + mutex_lock(&adapter->ptm_lock);
> +
> + ret = get_device_system_crosststamp(igc_phc_get_syncdevicetime,
> + adapter, &adapter->snapshot, cts);
> + mutex_unlock(&adapter->ptm_lock);
> +
> + return ret;
> }
>
> static int igc_ptp_getcyclesx64(struct ptp_clock_info *ptp,
> @@ -1169,6 +1176,7 @@ void igc_ptp_init(struct igc_adapter *adapter)
> spin_lock_init(&adapter->ptp_tx_lock);
> spin_lock_init(&adapter->free_timer_lock);
> spin_lock_init(&adapter->tmreg_lock);
> + mutex_init(&adapter->ptm_lock);
I believe there should be a corresponding mutex_destroy()?
Thanks,
Tony
> adapter->tstamp_config.rx_filter = HWTSTAMP_FILTER_NONE;
> adapter->tstamp_config.tx_type = HWTSTAMP_TX_OFF;
next prev parent reply other threads:[~2024-10-29 21:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 2:30 [PATCH iwl-net v2 0/4] igc: Fix PTM timeout Chris H
2024-10-23 2:30 ` [PATCH iwl-net v2 1/4] igc: Ensure the PTM cycle is reliably triggered Chris H
2024-10-29 21:21 ` Tony Nguyen
2024-10-30 10:17 ` Corinna Vinschen
2024-10-31 9:34 ` [Intel-wired-lan] " Avigail Dahan
2024-10-23 2:30 ` [PATCH iwl-net v2 2/4] igc: Lengthen the hardware retry time to prevent timeouts Chris H
2024-10-31 9:35 ` [Intel-wired-lan] " Avigail Dahan
2024-10-23 2:30 ` [PATCH iwl-net v2 3/4] igc: Move ktime snapshot into PTM retry loop Chris H
2024-10-31 9:35 ` [Intel-wired-lan] " Mor Bar-Gabay
2024-10-23 2:30 ` [PATCH iwl-net v2 4/4] igc: Add lock preventing multiple simultaneous PTM transactions Chris H
2024-10-29 21:20 ` Tony Nguyen [this message]
2024-10-30 10:20 ` Corinna Vinschen
2024-10-31 9:36 ` [Intel-wired-lan] " Mor Bar-Gabay
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=b22e920a-34c9-4926-9cf1-02dc24fcfb77@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=christopher.s.hall@intel.com \
--cc=david.zage@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--cc=rodrigo.cadore@l-acoustics.com \
--cc=vinicius.gomes@intel.com \
--cc=vinschen@redhat.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).