From: Dave Jiang <dave.jiang@intel.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: linux-cxl@vger.kernel.org, alejandro.lucero-palau@amd.com,
dan.j.williams@intel.com, ira.weiny@intel.com,
vishal.l.verma@intel.com, Jonathan.Cameron@huawei.com,
dave@stgolabs.net, fan.ni@samsung.com,
Alejandro Lucero <alucerop@amd.com>
Subject: Re: [PATCH v2 1/2] cxl: Move mailbox related bits to the same context
Date: Thu, 29 Aug 2024 08:51:27 -0700 [thread overview]
Message-ID: <5e33f39b-4be9-47dd-ac58-5be87023112c@intel.com> (raw)
In-Reply-To: <ZtCWmAxX8766Blpj@aschofie-mobl2.lan>
On 8/29/24 8:41 AM, Alison Schofield wrote:
> On Tue, Aug 27, 2024 at 02:49:49PM -0700, Dave Jiang wrote:
>> Create a new 'struct cxl_mailbox' and move all mailbox related bits to
>> it. This allows isolation of all CXL mailbox data in order to export
>> some of the calls to external callers and avoid exporting of CXL driver
>> specific bits such has device states. The allocation of
>> 'struct cxl_mailbox' is also split out with cxl_mailbox_create() so the
>> mailbox can be created independently.
>
> The reasoning for this mentions 'external callers' yet this new struct
> is added to a header file that is still internal to the kernel. It's
> now available outside the CXL driver but not externally.
>
> Does it belong in to include/uapi/linux/ and need to be documented
> in the driver-api/cxl/ (same as cxl_mem.h)
>
external as to CXL but still kernel caller. this is not for user space consumption. for example future fwctl cxl support or maybe type2 support Alejandro is working on.
> If it stays internal to include/linux/ note that cxl-event.h
> already exists there w no 'cxl' subdir'. Maybe skip the subdir
> addition, or mv cxl-event.h along with.
yeah I need to move cxl-event.h into that dir as well. missed that.
>
> --Alison
>
> snip
>
>
next prev parent reply other threads:[~2024-08-29 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 21:49 [PATCH 0/2 v2] cxl: Pull out mailbox bits to be independent of cxl_dev_state Dave Jiang
2024-08-27 21:49 ` [PATCH v2 1/2] cxl: Move mailbox related bits to the same context Dave Jiang
2024-08-28 11:54 ` Jonathan Cameron
2024-08-29 15:41 ` Alison Schofield
2024-08-29 15:51 ` Dave Jiang [this message]
2024-08-29 16:50 ` Alison Schofield
2024-08-27 21:49 ` [PATCH v2 2/2] cxl: Convert cxl_internal_send_cmd() to use 'struct cxl_mailbox' as input Dave Jiang
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=5e33f39b-4be9-47dd-ac58-5be87023112c@intel.com \
--to=dave.jiang@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alejandro.lucero-palau@amd.com \
--cc=alison.schofield@intel.com \
--cc=alucerop@amd.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=vishal.l.verma@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