From: "Dan Williams (nvidia)" <djbw@kernel.org>
To: Alejandro Lucero Palau <alucerop@amd.com>,
"Dan Williams (nvidia)" <djbw@kernel.org>,
alejandro.lucero-palau@amd.com, linux-cxl@vger.kernel.org,
netdev@vger.kernel.org, edward.cree@amd.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, dave.jiang@intel.com
Cc: Dan Williams <dan.j.williams@intel.com>,
Ben Cheatham <benjamin.cheatham@amd.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH v27 3/5] cxl/sfc: Initialize dpa without a mailbox
Date: Tue, 16 Jun 2026 12:35:16 -0700 [thread overview]
Message-ID: <6a31a5742e552_9b855100d5@djbw-dev.notmuch> (raw)
In-Reply-To: <17b68fb1-768e-49f6-884d-49e0952621b8@amd.com>
Alejandro Lucero Palau wrote:
>
> On 6/10/26 00:24, Dan Williams (nvidia) wrote:
> > alejandro.lucero-palau@ wrote:
> >> From: Alejandro Lucero <alucerop@amd.com>
> >>
> >> Type3 relies on mailbox CXL_MBOX_OP_IDENTIFY command for initializing
> >> memdev state params which end up being used for DPA initialization.
> >>
> >> Allow a Type2 driver to initialize DPA simply by giving the size of its
> >> volatile hardware partition.
> >>
> >> Move related functions to memdev.
> > The code movement is not strictly necessary. Just add cxl_set_capacity()
> > and we can consider a move later if mbox.o and memdev.o are ever not
> > both included in cxl_core.o by default.
>
>
> I think it is the right thing to do as the new function uses add_part()
> (moved) and the other add_part() client is the other function moved,
> cxl_mem_dpa_fetch().
>
> Note cxl_mem_get_partition() used by cxl_mem_dpa_fetch() is the one
> working with mbox commands and it remains in the same place inside
> core/mbox.c and the only cxl_mem_dpa_fetch() client is cxl/pci.c
>
>
> This was reviewed and accepted so no reason for not doing it ...
Sure, I am ok to let it go as is.
next prev parent reply other threads:[~2026-06-16 19:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 21:57 [PATCH v27 0/5] Type2 device basic support alejandro.lucero-palau
2026-06-09 21:57 ` [PATCH v27 1/5] sfc: add cxl support alejandro.lucero-palau
2026-06-09 21:57 ` [PATCH v27 2/5] cxl/sfc: Map cxl regs alejandro.lucero-palau
2026-06-09 21:57 ` [PATCH v27 3/5] cxl/sfc: Initialize dpa without a mailbox alejandro.lucero-palau
2026-06-09 23:24 ` Dan Williams (nvidia)
2026-06-10 6:03 ` Alejandro Lucero Palau
2026-06-16 19:35 ` Dan Williams (nvidia) [this message]
2026-06-09 21:57 ` [PATCH v27 4/5] sfc: obtain and map cxl range using devm_cxl_probe_mem alejandro.lucero-palau
2026-06-09 21:58 ` Dave Jiang
2026-06-10 5:48 ` Alejandro Lucero Palau
2026-06-09 23:30 ` Dan Williams (nvidia)
2026-06-10 6:10 ` Alejandro Lucero Palau
2026-06-10 13:56 ` Alejandro Lucero Palau
2026-06-15 14:47 ` Alejandro Lucero Palau
2026-06-16 19:51 ` Dan Williams (nvidia)
2026-06-09 21:57 ` [PATCH v27 5/5] sfc: support pio mapping based on cxl alejandro.lucero-palau
2026-06-09 22:18 ` Dave Jiang
2026-06-10 5:50 ` Alejandro Lucero Palau
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=6a31a5742e552_9b855100d5@djbw-dev.notmuch \
--to=djbw@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=alejandro.lucero-palau@amd.com \
--cc=alucerop@amd.com \
--cc=benjamin.cheatham@amd.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=edward.cree@amd.com \
--cc=kuba@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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