From: Ray Kinsella <mdr@ashroe.eu>
To: Srikanth Yalavarthi <syalavarthi@marvell.com>
Cc: dev@dpdk.org, jerinj@marvell.com, sshankarnara@marvell.com
Subject: Re: [PATCH v2 1/1] eal: add internal function to get base address
Date: Tue, 18 Jan 2022 07:35:43 -0500 [thread overview]
Message-ID: <87h7a1z0f4.fsf@mdr78.vserver.site> (raw)
In-Reply-To: <20220117133023.12768-1-syalavarthi@marvell.com>
Srikanth Yalavarthi <syalavarthi@marvell.com> writes:
> Added an internal helper to get OS-specific EAL mappping base addreess
mapping
address
>
> This helper can be used by the drivers to map host address range with
> offload devices and would be need for device specific operations like
> firmware load
>
> Signed-off-by: Srikanth Yalavarthi <syalavarthi@marvell.com>
> ---
>
> v2:
> * Dropped Change-Id
>
> lib/eal/common/eal_common_config.c | 7 +++++++
> lib/eal/include/rte_eal.h | 9 +++++++++
> lib/eal/version.map | 1 +
> 3 files changed, 17 insertions(+)
>
> diff --git a/lib/eal/common/eal_common_config.c b/lib/eal/common/eal_common_config.c
> index 1c4c4dd585..cec4991d96 100644
> --- a/lib/eal/common/eal_common_config.c
> +++ b/lib/eal/common/eal_common_config.c
> @@ -87,3 +87,10 @@ rte_eal_has_pci(void)
> {
> return !internal_config.no_pci;
> }
> +
> +/* Get the EAL base address */
> +uint64_t
> +rte_eal_get_baseaddr(void)
> +{
> + return eal_get_baseaddr();
> +}
> diff --git a/lib/eal/include/rte_eal.h b/lib/eal/include/rte_eal.h
> index 5a34a6acd9..29298c3c83 100644
> --- a/lib/eal/include/rte_eal.h
> +++ b/lib/eal/include/rte_eal.h
> @@ -475,6 +475,15 @@ rte_eal_mbuf_user_pool_ops(void);
> const char *
> rte_eal_get_runtime_dir(void);
>
> +/**
> + * Get the OS-specific EAL base address.
> + *
> + * @return
> + * The base address.
> + */
> +__rte_internal
> +uint64_t rte_eal_get_baseaddr(void);
> +
> #ifdef __cplusplus
> }
> #endif
> diff --git a/lib/eal/version.map b/lib/eal/version.map
> index ab28c22791..b53eeb30d7 100644
> --- a/lib/eal/version.map
> +++ b/lib/eal/version.map
> @@ -425,6 +425,7 @@ EXPERIMENTAL {
> INTERNAL {
> global:
>
> + rte_eal_get_baseaddr;
> rte_firmware_read;
> rte_intr_allow_others;
> rte_intr_cap_multiple;
Acked-by: Ray Kinsella <mdr@ashroe.eu>
--
Regards, Ray K
prev parent reply other threads:[~2022-01-18 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 13:30 Srikanth Yalavarthi
2022-01-18 12:35 ` Ray Kinsella [this message]
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=87h7a1z0f4.fsf@mdr78.vserver.site \
--to=mdr@ashroe.eu \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=sshankarnara@marvell.com \
--cc=syalavarthi@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).