DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@oss.nxp.com>
To: David Marchand <david.marchand@redhat.com>,
	Prashant Gupta <prashant.gupta_3@nxp.com>
Cc: stephen@networkplumber.org, hemant.agrawal@nxp.com, dev@dpdk.org
Subject: Re: [PATCH] bus/dpaa: defer bus initialization to probe
Date: Thu, 27 Aug 2026 21:32:31 +0530	[thread overview]
Message-ID: <0a6a1dff-1bee-49aa-bee3-946e13d80daf@oss.nxp.com> (raw)
In-Reply-To: <CAJFAV8yZBb7mQb+cEyuq_XnbQTaFxntTXz0sUm3NCMYsT0eDDg@mail.gmail.com>


On 27-08-2026 14:24, David Marchand wrote:
> Hello,
>
> On Thu, 27 Aug 2026 at 09:37, Prashant Gupta <prashant.gupta_3@nxp.com> wrote:
>> In the DPAA bus initialization: it builds the
>> device list, loads the QMAN/BMAN drivers, registers the platform mbuf
>> pool ops and populates the PA to VA translation table. All of it needs
>> the DPDK heap or a memzone for multi process scenarios.
>>
>> get_iommu_class() for this bus only checks two sysfs paths, so the
>> initialization is not needed in scan to report the IOVA mode. Move it
>> back to probe.
>>
>> Fixes: cdefd2e980bd ("drivers/bus: initialize NXP bus specifics in scan")
>>
>> Signed-off-by: Prashant Gupta <prashant.gupta_3@nxp.com>
> While the change looks correct, I don't understand what is being fixed.
> Could you elaborate on the issue?
>
In my brief discussion about this issue, I was told that some of the 
these QMAN/BMAN related initialization should be done using 
shared/Hugepage memory for multi-process sharing;

Hugepages are not available during scan, they become available later.

Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>

>

      reply	other threads:[~2026-08-27 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27  7:28 [PATCH] bus/dpaa: defer bus initialization to probe Prashant Gupta
2026-08-27  8:54 ` David Marchand
2026-08-27 16:02   ` Hemant Agrawal [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=0a6a1dff-1bee-49aa-bee3-946e13d80daf@oss.nxp.com \
    --to=hemant.agrawal@oss.nxp.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=prashant.gupta_3@nxp.com \
    --cc=stephen@networkplumber.org \
    /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