DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Vamsi Krishna <vattunuru@marvell.com>
Cc: jerinj@marvell.com, dev@dpdk.org
Subject: Re: [PATCH v2 1/1] net/octeon_ep: add device removal event callback
Date: Tue, 1 Oct 2024 13:47:41 +0530	[thread overview]
Message-ID: <CALBAE1OL3muMRLmtRtPqHqbKXSg5cK3baMNH3KoZZ2cWUex_bg@mail.gmail.com> (raw)
In-Reply-To: <20240920044347.1211530-1-vattunuru@marvell.com>

On Fri, Sep 20, 2024 at 10:14 AM Vamsi Krishna <vattunuru@marvell.com> wrote:
>
> From: Vamsi Attunuru <vattunuru@marvell.com>
>
> Adds an event callback to catch any device removal
> event occurred during driver probe. This callback helps
> in terminating the execution if there is any device removal
> event during the driver probe.
>
> Also moved global register configuration into dev_configure()
> routine and also validates register reads for any invalid
> return values from hardware during driver probe.
>
> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
> ---
> V2 changes:
> * Corrected commit message
> * Updated release notes
> * Used UINT64_MAX macro.
>
>  doc/guides/rel_notes/release_24_11.rst |  5 +++
>  drivers/net/octeon_ep/cnxk_ep_vf.c     |  2 +
>  drivers/net/octeon_ep/otx2_ep_vf.c     |  2 +
>  drivers/net/octeon_ep/otx_ep_ethdev.c  | 58 +++++++++++++++++++-------
>  drivers/net/octeon_ep/otx_ep_mbox.c    | 11 +++++
>  drivers/net/octeon_ep/otx_ep_vf.c      |  2 +
>  6 files changed, 64 insertions(+), 16 deletions(-)
>
> diff --git a/doc/guides/rel_notes/release_24_11.rst b/doc/guides/rel_notes/release_24_11.rst
> index 0ff70d9057..ffb2d13a76 100644
> --- a/doc/guides/rel_notes/release_24_11.rst
> +++ b/doc/guides/rel_notes/release_24_11.rst
> @@ -68,6 +68,11 @@ Removed Items
>     Also, make sure to start the actual text at the margin.
>     =======================================================
>
> +* **Added device removal event callback in octeon_ep driver.**
> +
> +  Added an event callback to catch any device removal event would occur during
> +  driver probe. This callback helps in terminating the execution if there is
> +  any device removal event during the driver probe.


Since the user may not be impacted with this, This update may not be needed.



>
> +static void
> +otx_epdev_event_callback(const char *device_name, enum rte_dev_event_type type,
> +                        __rte_unused void *arg)
> +{
> +       if (type == RTE_DEV_EVENT_REMOVE)
> +               otx_ep_info("Octeon epdev: %s has been removed!\n", device_name);

Please add good amount of comment here. i.e Purpose and how

> +       RTE_VERIFY(type != RTE_DEV_EVENT_REMOVE);
> +}
> +

  reply	other threads:[~2024-10-01  8:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27  5:32 [PATCH] " Vamsi Krishna
2024-09-19 18:18 ` Jerin Jacob
2024-09-20  3:48   ` [EXTERNAL] " Vamsi Krishna Attunuru
2024-09-20  4:43 ` [PATCH v2 1/1] " Vamsi Krishna
2024-10-01  8:17   ` Jerin Jacob [this message]
2024-10-01  8:38   ` [PATCH v3 " Vamsi Krishna

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=CALBAE1OL3muMRLmtRtPqHqbKXSg5cK3baMNH3KoZZ2cWUex_bg@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=vattunuru@marvell.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).