DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Lavanya Govindarajan <lavanyax.govindarajan@intel.com>
Cc: dev <dev@dpdk.org>, "Pattan, Reshma" <reshma.pattan@intel.com>,
	 "Burakov, Anatoly" <anatoly.burakov@intel.com>,
	 "Parthasarathy, JananeeX M" <jananeex.m.parthasarathy@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] test/eal: add ut for eal options proc-type and uio
Date: Tue, 2 Jul 2019 09:33:04 +0200	[thread overview]
Message-ID: <CAJFAV8zL0hq0enK9D7HZ5UnBkgwgT-mD2Mkd+p40KWrVu9Nk=w@mail.gmail.com> (raw)
In-Reply-To: <1561637559-27164-1-git-send-email-lavanyax.govindarajan@intel.com>

On Thu, Jun 27, 2019 at 2:18 PM Lavanya Govindarajan <
lavanyax.govindarajan@intel.com> wrote:

> Added unit test cases for EAL flags --proc-type=auto and
> --create-uio-dev in order to cover the below functions
> eal_proc_type_detect()
> rte_eal_create_uio_dev()
>
> Signed-off-by: Lavanya Govindarajan <lavanyax.govindarajan@intel.com>
> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
> v2: Removed core and channels eal options as they are not significant
> ---
>
>  app/test/test_eal_flags.c | 27 +++++++++++++++++++++++++++
>  1 file changed, 27 insertions(+)
>
> diff --git a/app/test/test_eal_flags.c b/app/test/test_eal_flags.c
> index 9112c96d0..17c0e43d2 100644
> --- a/app/test/test_eal_flags.c
> +++ b/app/test/test_eal_flags.c
> @@ -880,6 +880,18 @@ test_misc_flags(void)
>         const char *argv15[] = {prgname, "--file-prefix=intr",
>                         "-c", "1", "-n", "2", "--vfio-intr=invalid"};
>
> +       /* With process type as auto-detect */
> +       const char * const argv16[] = {prgname, "--file-prefix=auto",
> +                       "--proc-type=auto"};
> +
> +       /* With process type as auto-detect with no-shconf */
> +       const char * const argv17[] = {prgname, "--proc-type=auto",
> +                       no_shconf, nosh_prefix, no_huge};
> +
> +       /* With process type as --create-uio-dev flag */
> +       const char * const argv18[] = {prgname, "--file-prefix=uiodev",
> +                       "--create-uio-dev"};
> +
>         /* run all tests also applicable to FreeBSD first */
>
>         if (launch_proc(argv0) == 0) {
> @@ -956,6 +968,21 @@ test_misc_flags(void)
>                                 "--vfio-intr invalid parameter\n");
>                 return -1;
>         }
> +       if (launch_proc(argv16) != 0) {
> +               printf("Error - process did not run ok with "
> +                               "--proc-type as auto parameter\n");
> +               return -1;
> +       }
> +       if (launch_proc(argv17) != 0) {
> +               printf("Error - process did not run ok with "
> +                               "--proc type as auto - no-shconf
> parameter\n");
>

Nit: those messages are not that useful, but at least let's make them
consistent by using the full option names: --proc-type and --no-shconf.


+               return -1;
> +       }
> +       if (launch_proc(argv18) != 0) {
> +               printf("Error - process did not run ok with "
> +                               "--create-uio-dev parameter\n");
> +               return -1;
> +       }
>         return 0;
>  }
>
> --
> 2.14.1
>
>
Reviewed-by: David Marchand <david.marchand@redhat.com>


-- 
David Marchand

  reply	other threads:[~2019-07-02  7:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21 13:50 [dpdk-dev] [PATCH] " Lavanya Govindarajan
2019-06-26  9:32 ` Burakov, Anatoly
2019-06-26  9:36 ` David Marchand
2019-06-27 12:12 ` [dpdk-dev] [PATCH v2] " Lavanya Govindarajan
2019-07-02  7:33   ` David Marchand [this message]
2019-07-03 13:06   ` [dpdk-dev] [PATCH v3] " Lavanya Govindarajan
2019-07-04 21:52     ` Thomas Monjalon

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='CAJFAV8zL0hq0enK9D7HZ5UnBkgwgT-mD2Mkd+p40KWrVu9Nk=w@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=jananeex.m.parthasarathy@intel.com \
    --cc=lavanyax.govindarajan@intel.com \
    --cc=reshma.pattan@intel.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).