From: Kory Maincent <kory.maincent@bootlin.com>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: davem@davemloft.net, Andrew Lunn <andrew@lunn.ch>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com,
linux-arm-kernel@lists.infradead.org,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Herve Codina <herve.codina@bootlin.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Simon Horman <horms@kernel.org>,
Romain Gantois <romain.gantois@bootlin.com>,
Piergiorgio Beruto <piergiorgio.beruto@gmail.com>,
Stanislav Fomichev <sdf@fomichev.me>
Subject: Re: [PATCH net-next v2 4/7] net: ethtool: netlink: Introduce per-phy DUMP helpers
Date: Mon, 10 Mar 2025 13:21:03 +0100 [thread overview]
Message-ID: <20250310132103.1312d1b6@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <20250308155440.267782-5-maxime.chevallier@bootlin.com>
On Sat, 8 Mar 2025 16:54:36 +0100
Maxime Chevallier <maxime.chevallier@bootlin.com> wrote:
> As there are multiple ethnl commands that report messages based on
> phy_device information, let's introduce a set of ethnl generic dump
> helpers to allow DUMP support for each PHY on a given netdev.
>
> This logic iterates over the phy_link_topology of each netdev (or a
> single netdev for filtered DUMP), and call ethnl_default_dump_one() with
> the req_info populated with ifindex + phyindex.
>
> This allows re-using all the existing infra for phy-targetting commands
> that already use ethnl generic helpers.
>
> Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
> ---
> V2: Rebase
>
> net/ethtool/netlink.c | 53 +++++++++++++++++++++++++++++++++++++++++++
> net/ethtool/netlink.h | 6 +++++
> 2 files changed, 59 insertions(+)
>
> diff --git a/net/ethtool/netlink.c b/net/ethtool/netlink.c
> index ae06b72239a8..a09bcd67b38f 100644
> --- a/net/ethtool/netlink.c
> +++ b/net/ethtool/netlink.c
> @@ -559,6 +559,59 @@ static int ethnl_default_dump_one(struct sk_buff *skb,
> return ret;
> }
>
> +/* Specific context for phy-targeting command DUMP operatins. We keep in
> context
> + * the latest phy_index we dumped, in case of an interrupted DUMP.
> + */
> +struct ethnl_dump_ctx_perphy {
> + unsigned long phy_index;
> +};
> +
> +int ethnl_dump_start_perphy(struct ethnl_dump_ctx *ctx)
Could you add comments or event better, kdoc for non static function to explain
their purpose.
> +{
> + struct ethnl_dump_ctx_perphy *dump_ctx;
> +
> + dump_ctx = kzalloc(sizeof(*dump_ctx), GFP_KERNEL);
> + if (!dump_ctx)
> + return -ENOMEM;
> +
> + ctx->cmd_ctx = dump_ctx;
> +
> + return 0;
> +}
> +
> +void ethnl_dump_done_perphy(struct ethnl_dump_ctx *ctx)
same.
> +{
> + kfree(ctx->cmd_ctx);
> +}
> +
> +int ethnl_dump_one_dev_perphy(struct sk_buff *skb,
> + struct ethnl_dump_ctx *ctx,
> + const struct genl_info *info)
same.
> +{
> + struct ethnl_dump_ctx_perphy *dump_ctx = ctx->cmd_ctx;
> + struct net_device *dev = ctx->reply_data->dev;
> + struct phy_device_node *pdn;
> + int ret = 0;
> +
> + if (!dev->link_topo)
> + return 0;
> +
> + xa_for_each_start(&dev->link_topo->phys, dump_ctx->phy_index,
> + pdn, dump_ctx->phy_index) {
> + ctx->req_info->phy_index = dump_ctx->phy_index;
> +
> + /* We can re-use the original dump_one as ->prepare_data in
> + * commands use ethnl_req_get_phydev(), which gets the PHY
> from
> + * what's in req_info
> + */
> + ret = ethnl_default_dump_one(skb, ctx, info);
> + if (ret)
> + break;
> + }
> +
> + return ret;
> +}
Regards,
---
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-03-10 12:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 15:54 [PATCH net-next v2 0/7] net: ethtool: Introduce ethnl dump helpers Maxime Chevallier
2025-03-08 15:54 ` [PATCH net-next v2 1/7] net: ethtool: netlink: Allow per-netdevice DUMP operations Maxime Chevallier
2025-03-10 10:58 ` Kory Maincent
2025-03-08 15:54 ` [PATCH net-next v2 2/7] net: ethtool: netlink: Rename ethnl_default_dump_one Maxime Chevallier
2025-03-08 15:54 ` [PATCH net-next v2 3/7] net: ethtool: netlink: Introduce command-specific dump_one_dev Maxime Chevallier
2025-03-08 15:54 ` [PATCH net-next v2 4/7] net: ethtool: netlink: Introduce per-phy DUMP helpers Maxime Chevallier
2025-03-10 12:21 ` Kory Maincent [this message]
2025-03-08 15:54 ` [PATCH net-next v2 5/7] net: ethtool: phy: Convert the PHY_GET command to generic phy dump Maxime Chevallier
2025-03-10 12:14 ` Kory Maincent
2025-03-08 15:54 ` [PATCH net-next v2 6/7] net: ethtool: plca: Use per-PHY DUMP operations Maxime Chevallier
2025-03-08 15:54 ` [PATCH net-next v2 7/7] net: ethtool: pse-pd: " Maxime Chevallier
2025-03-10 12:23 ` Kory Maincent
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=20250310132103.1312d1b6@kmaincent-XPS-13-7390 \
--to=kory.maincent@bootlin.com \
--cc=andrew@lunn.ch \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=herve.codina@bootlin.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=piergiorgio.beruto@gmail.com \
--cc=romain.gantois@bootlin.com \
--cc=sdf@fomichev.me \
--cc=thomas.petazzoni@bootlin.com \
--cc=vladimir.oltean@nxp.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