From: Dan Williams <dan.j.williams@intel.com>
To: Gregory Price <gregory.price@memverge.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
<linux-cxl@vger.kernel.org>
Subject: Re: [GIT preview] for-6.3/cxl-ram-region
Date: Mon, 30 Jan 2023 15:18:38 -0800 [thread overview]
Message-ID: <63d8504ecaa5_ea222294f4@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <Y9gva49IPFOXYlkH@memverge.com>
Gregory Price wrote:
> On Mon, Jan 30, 2023 at 12:10:08PM -0800, Dan Williams wrote:
> > Gregory Price wrote:
> > [..]
> > > I found the same results.
> > > echo mem0 > /sys/bus/cxl/devices/region0/target0
> > >
> > > Not sure if bug/missing feature, but after attaching a device to the
> > > target, you get no output when reading target0
> > >
> > > ```
> > > [root@fedora ~]# cat /sys/bus/cxl/devices/region0/target0
> > >
> > > [root@fedora ~]#
> >
> > Hmm, did you not get:
> >
> > "-bash: echo: write error: Invalid argument"
> >
> > ...at that step? Because targetX expects an endpoint decoder, not a
> > memdev.
> >
>
> ¯\_(ツ)_/¯ bug?
>
> I went through the kernel code and thought it was looking for a memdev
> but i guess i was wrong
>
> // ... snip ...
> dev = bus_find_device_by_name(&cxl_bus_type, NULL, buf);
> if (!dev)
> return -ENODEV;
>
> if (!is_endpoint_decoder(dev)) {
> rc = -EINVAL;
> goto out;
> }
> // ... snip ...
Oh, yes, it is a bug. I fixed it up when I address this 0day report:
https://lore.kernel.org/linux-cxl/202301281313.kVrIreUj-lkp@intel.com/
...I posted another spin of that branch with that fixed up.
next prev parent reply other threads:[~2023-01-30 23:19 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 [this message]
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
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=63d8504ecaa5_ea222294f4@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.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