From: Alison Schofield <alison.schofield@intel.com>
To: Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
Dave Jiang <dave.jiang@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
"Dan Williams" <dan.j.williams@intel.com>,
<linux-cxl@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] cxl/region: Refactor address translation funcs for testing
Date: Tue, 9 Sep 2025 10:45:25 -0700 [thread overview]
Message-ID: <aMBnteQTnLZRwfvK@aschofie-mobl2.lan> (raw)
In-Reply-To: <20250909171005.000040f6@huawei.com>
On Tue, Sep 09, 2025 at 05:10:05PM +0100, Jonathan Cameron wrote:
> On Fri, 29 Aug 2025 00:21:25 -0700
> Alison Schofield <alison.schofield@intel.com> wrote:
>
> > In preparation for adding a test module that exercises the address
> > translation calculations, extract the core calculations into stand-
> > alone functions that operate on base parameters without dependencies
> > on struct cxl_region.
> >
> > Mark the new functions as static outside of test builds by adding
> > and using a new __mock_export label.
>
> For the __mock_exports magic, I assume that can be applied in existing
> cases as well. Perhaps better to introduce it for them first?
> That would give a nice clear example of what changes.
I came upon this new-ish helper and intend to replace the __mock_exports
magic with it in the next revision of this set.
707f853d7fa3 ("module: Provide EXPORT_SYMBOL_GPL_FOR_MODULES() helper")
I think the existing cxl_num_decoders_committed can use the helper too,
and if that works out I'll present it first as an example of using the
new helper as you suggest.
Thanks for the review!
>
next prev parent reply other threads:[~2025-09-09 17:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 7:21 [PATCH v2 0/3] CXL: Add a loadable module for address translation Alison Schofield
2025-08-29 7:21 ` [PATCH v2 1/3] cxl/region: Refactor address translation funcs for testing Alison Schofield
2025-09-04 22:05 ` Dave Jiang
2025-09-09 17:31 ` Alison Schofield
2025-09-09 16:10 ` Jonathan Cameron
2025-09-09 17:45 ` Alison Schofield [this message]
2025-09-10 12:32 ` Jonathan Cameron
2025-08-29 7:21 ` [PATCH v2 2/3] cxl/acpi: Make the XOR calculations available " Alison Schofield
2025-09-04 23:21 ` Dave Jiang
2025-09-09 17:33 ` Alison Schofield
2025-08-29 7:21 ` [PATCH v2 3/3] cxl/test: Add cxl_translate module for address translation testing Alison Schofield
2025-09-04 23:24 ` 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=aMBnteQTnLZRwfvK@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.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