From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>,
"gregory.price@memverge.com" <gregory.price@memverge.com>
Cc: "Jonathan.Cameron@huawei.com" <Jonathan.Cameron@huawei.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Subject: Re: [GIT preview] for-6.3/cxl-ram-region
Date: Tue, 31 Jan 2023 17:59:26 +0000 [thread overview]
Message-ID: <51d8e1a83fa70c2caf2835381eadea5f96d27892.camel@intel.com> (raw)
In-Reply-To: <Y9h2VhGuraZfEJfD@memverge.com>
On Mon, 2023-01-30 at 21:00 -0500, Gregory Price wrote:
> On Mon, Jan 30, 2023 at 03:18:38PM -0800, Dan Williams wrote:
>
>
> This worked for me, though it took me a bit to figure out how to wire
> everythign up - still not sure this is entirely correct but this is the
> string of commands that were required to successfully attach an endpoint
> decoder to the root decoder.
>
> Note: The root decoder has interleave_(granularity=256, ways=1), and the
> region code appears to require the same granularity? Does that mean
> we're stuck to 256b granularity? (unless i misread the code, which i'm
> about 75% sure i am).
>
>
> Command string:
>
> # Program the endpoint decoder for ram of size 1GB
> echo ram > /sys/bus/cxl/devices/decoder2.0/mode
> echo 0x40000000 > /sys/bus/cxl/devices/decoder2.0/dpa_size
>
> # Create a region in the root decoder
> echo region0 > /sys/bus/cxl/devices/decoder0.0/create_ram_region
>
> # Configure that region with the same interleave granularity
> # and ways as the root and endpoint decoders
> echo 256 > /sys/bus/cxl/devices/region0/interleave_granularity
> echo 1 > /sys/bus/cxl/devices/region0/interleave_ways
> echo 0x40000000 > /sys/bus/cxl/devices/region0/size
>
> # Link the endpoint decoder as a target in the region
> echo decoder2.0 > /sys/bus/cxl/devices/region0/target0
>
> # Commit the changes
> echo 1 > /sys/bus/cxl/devices/region0/commit
I've pushed a cxl-cli branch[1] that incorporates this flow, and allows
for: cxl create-region -t ram <other options>
Feel free to give it a spin!
[1]: https://github.com/pmem/ndctl/commits/vv/volatile-regions
next prev parent reply other threads:[~2023-01-31 18:00 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 6:25 [GIT preview] for-6.3/cxl-ram-region Dan Williams
2023-01-26 6:29 ` Dan Williams
2023-01-26 18:50 ` Jonathan Cameron
2023-01-26 19:34 ` Jonathan Cameron
2023-01-30 14:16 ` Gregory Price
2023-01-30 20:10 ` Dan Williams
2023-01-30 20:58 ` Gregory Price
2023-01-30 23:18 ` Dan Williams
2023-01-30 22:00 ` Gregory Price
2023-01-31 2:00 ` Gregory Price
2023-01-31 16:56 ` Dan Williams
2023-01-31 17:59 ` Verma, Vishal L [this message]
2023-01-31 19:03 ` Gregory Price
2023-01-31 19:46 ` Verma, Vishal L
2023-01-31 20:24 ` Verma, Vishal L
2023-01-31 23:03 ` Gregory Price
2023-01-31 23:17 ` Gregory Price
2023-01-31 23:50 ` Fan Ni
2023-02-01 5:29 ` Gregory Price
2023-02-01 21:16 ` Gregory Price
2023-02-02 1:06 ` Gregory Price
2023-02-02 16:03 ` Jonathan Cameron
2023-02-01 22:05 ` Gregory Price
2023-02-02 18:13 ` Jonathan Cameron
2023-02-02 0:43 ` Gregory Price
2023-02-02 18:18 ` Dan Williams
2023-02-02 0:44 ` Gregory Price
2023-02-07 16:31 ` Jonathan Cameron
2023-01-30 14:23 ` Gregory Price
2023-01-31 14:56 ` Jonathan Cameron
2023-01-31 17:34 ` Gregory Price
2023-01-26 22:05 ` Gregory Price
2023-01-26 22:20 ` Dan Williams
2023-02-04 2:36 ` Dan Williams
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=51d8e1a83fa70c2caf2835381eadea5f96d27892.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=gregory.price@memverge.com \
--cc=linux-cxl@vger.kernel.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