From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Bobo WL <lmw.bobo@gmail.com>, <linux-cxl@vger.kernel.org>,
<qemu-devel@nongnu.org>, <qemu-arm@nongnu.org>
Subject: Re: [BUG] cxl can not create region
Date: Wed, 17 Aug 2022 17:16:19 +0100 [thread overview]
Message-ID: <20220817171619.000021ca@huawei.com> (raw)
In-Reply-To: <62f5a2ffe8be0_3ce68294a4@dwillia2-xfh.jf.intel.com.notmuch>
On Thu, 11 Aug 2022 17:46:55 -0700
Dan Williams <dan.j.williams@intel.com> wrote:
> Dan Williams wrote:
> > Bobo WL wrote:
> > > Hi Dan,
> > >
> > > Thanks for your reply!
> > >
> > > On Mon, Aug 8, 2022 at 11:58 PM Dan Williams <dan.j.williams@intel.com> wrote:
> > > >
> > > > What is the output of:
> > > >
> > > > cxl list -MDTu -d decoder0.0
> > > >
> > > > ...? It might be the case that mem1 cannot be mapped by decoder0.0, or
> > > > at least not in the specified order, or that validation check is broken.
> > >
> > > Command "cxl list -MDTu -d decoder0.0" output:
> >
> > Thanks for this, I think I know the problem, but will try some
> > experiments with cxl_test first.
>
> Hmm, so my cxl_test experiment unfortunately passed so I'm not
> reproducing the failure mode. This is the result of creating x4 region
> with devices directly attached to a single host-bridge:
>
> # cxl create-region -d decoder3.5 -w 4 -m -g 256 mem{12,10,9,11} -s $((1<<30))
> {
> "region":"region8",
> "resource":"0xf1f0000000",
> "size":"1024.00 MiB (1073.74 MB)",
> "interleave_ways":4,
> "interleave_granularity":256,
> "decode_state":"commit",
> "mappings":[
> {
> "position":3,
> "memdev":"mem11",
> "decoder":"decoder21.0"
> },
> {
> "position":2,
> "memdev":"mem9",
> "decoder":"decoder19.0"
> },
> {
> "position":1,
> "memdev":"mem10",
> "decoder":"decoder20.0"
> },
> {
> "position":0,
> "memdev":"mem12",
> "decoder":"decoder22.0"
> }
> ]
> }
> cxl region: cmd_create_region: created 1 region
>
> > Did the commit_store() crash stop reproducing with latest cxl/preview
> > branch?
>
> I missed the answer to this question.
>
> All of these changes are now in Linus' tree perhaps give that a try and
> post the debug log again?
Hi Dan,
I've moved onto looking at this one.
1 HB, 2RP (to make it configure the HDM decoder in the QEMU HB, I'll tidy that up
at some stage), 1 switch, 4 downstream switch ports each with a type 3
I'm not getting a crash, but can't successfully setup a region.
Upon adding the final target
It's failing in check_last_peer() as pos < distance.
Seems distance is 4 which makes me think it's using the wrong level of the heirarchy for
some reason or that distance check is wrong.
Wasn't a good idea to just skip that step though as it goes boom - though
stack trace is not useful.
Jonathan
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron via <qemu-arm@nongnu.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Bobo WL <lmw.bobo@gmail.com>, <linux-cxl@vger.kernel.org>,
<qemu-devel@nongnu.org>, <qemu-arm@nongnu.org>
Subject: Re: [BUG] cxl can not create region
Date: Wed, 17 Aug 2022 17:16:19 +0100 [thread overview]
Message-ID: <20220817171619.000021ca@huawei.com> (raw)
In-Reply-To: <62f5a2ffe8be0_3ce68294a4@dwillia2-xfh.jf.intel.com.notmuch>
On Thu, 11 Aug 2022 17:46:55 -0700
Dan Williams <dan.j.williams@intel.com> wrote:
> Dan Williams wrote:
> > Bobo WL wrote:
> > > Hi Dan,
> > >
> > > Thanks for your reply!
> > >
> > > On Mon, Aug 8, 2022 at 11:58 PM Dan Williams <dan.j.williams@intel.com> wrote:
> > > >
> > > > What is the output of:
> > > >
> > > > cxl list -MDTu -d decoder0.0
> > > >
> > > > ...? It might be the case that mem1 cannot be mapped by decoder0.0, or
> > > > at least not in the specified order, or that validation check is broken.
> > >
> > > Command "cxl list -MDTu -d decoder0.0" output:
> >
> > Thanks for this, I think I know the problem, but will try some
> > experiments with cxl_test first.
>
> Hmm, so my cxl_test experiment unfortunately passed so I'm not
> reproducing the failure mode. This is the result of creating x4 region
> with devices directly attached to a single host-bridge:
>
> # cxl create-region -d decoder3.5 -w 4 -m -g 256 mem{12,10,9,11} -s $((1<<30))
> {
> "region":"region8",
> "resource":"0xf1f0000000",
> "size":"1024.00 MiB (1073.74 MB)",
> "interleave_ways":4,
> "interleave_granularity":256,
> "decode_state":"commit",
> "mappings":[
> {
> "position":3,
> "memdev":"mem11",
> "decoder":"decoder21.0"
> },
> {
> "position":2,
> "memdev":"mem9",
> "decoder":"decoder19.0"
> },
> {
> "position":1,
> "memdev":"mem10",
> "decoder":"decoder20.0"
> },
> {
> "position":0,
> "memdev":"mem12",
> "decoder":"decoder22.0"
> }
> ]
> }
> cxl region: cmd_create_region: created 1 region
>
> > Did the commit_store() crash stop reproducing with latest cxl/preview
> > branch?
>
> I missed the answer to this question.
>
> All of these changes are now in Linus' tree perhaps give that a try and
> post the debug log again?
Hi Dan,
I've moved onto looking at this one.
1 HB, 2RP (to make it configure the HDM decoder in the QEMU HB, I'll tidy that up
at some stage), 1 switch, 4 downstream switch ports each with a type 3
I'm not getting a crash, but can't successfully setup a region.
Upon adding the final target
It's failing in check_last_peer() as pos < distance.
Seems distance is 4 which makes me think it's using the wrong level of the heirarchy for
some reason or that distance check is wrong.
Wasn't a good idea to just skip that step though as it goes boom - though
stack trace is not useful.
Jonathan
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Bobo WL <lmw.bobo@gmail.com>, <linux-cxl@vger.kernel.org>,
<qemu-devel@nongnu.org>, <qemu-arm@nongnu.org>
Subject: Re: [BUG] cxl can not create region
Date: Wed, 17 Aug 2022 17:16:19 +0100 [thread overview]
Message-ID: <20220817171619.000021ca@huawei.com> (raw)
In-Reply-To: <62f5a2ffe8be0_3ce68294a4@dwillia2-xfh.jf.intel.com.notmuch>
On Thu, 11 Aug 2022 17:46:55 -0700
Dan Williams <dan.j.williams@intel.com> wrote:
> Dan Williams wrote:
> > Bobo WL wrote:
> > > Hi Dan,
> > >
> > > Thanks for your reply!
> > >
> > > On Mon, Aug 8, 2022 at 11:58 PM Dan Williams <dan.j.williams@intel.com> wrote:
> > > >
> > > > What is the output of:
> > > >
> > > > cxl list -MDTu -d decoder0.0
> > > >
> > > > ...? It might be the case that mem1 cannot be mapped by decoder0.0, or
> > > > at least not in the specified order, or that validation check is broken.
> > >
> > > Command "cxl list -MDTu -d decoder0.0" output:
> >
> > Thanks for this, I think I know the problem, but will try some
> > experiments with cxl_test first.
>
> Hmm, so my cxl_test experiment unfortunately passed so I'm not
> reproducing the failure mode. This is the result of creating x4 region
> with devices directly attached to a single host-bridge:
>
> # cxl create-region -d decoder3.5 -w 4 -m -g 256 mem{12,10,9,11} -s $((1<<30))
> {
> "region":"region8",
> "resource":"0xf1f0000000",
> "size":"1024.00 MiB (1073.74 MB)",
> "interleave_ways":4,
> "interleave_granularity":256,
> "decode_state":"commit",
> "mappings":[
> {
> "position":3,
> "memdev":"mem11",
> "decoder":"decoder21.0"
> },
> {
> "position":2,
> "memdev":"mem9",
> "decoder":"decoder19.0"
> },
> {
> "position":1,
> "memdev":"mem10",
> "decoder":"decoder20.0"
> },
> {
> "position":0,
> "memdev":"mem12",
> "decoder":"decoder22.0"
> }
> ]
> }
> cxl region: cmd_create_region: created 1 region
>
> > Did the commit_store() crash stop reproducing with latest cxl/preview
> > branch?
>
> I missed the answer to this question.
>
> All of these changes are now in Linus' tree perhaps give that a try and
> post the debug log again?
Hi Dan,
I've moved onto looking at this one.
1 HB, 2RP (to make it configure the HDM decoder in the QEMU HB, I'll tidy that up
at some stage), 1 switch, 4 downstream switch ports each with a type 3
I'm not getting a crash, but can't successfully setup a region.
Upon adding the final target
It's failing in check_last_peer() as pos < distance.
Seems distance is 4 which makes me think it's using the wrong level of the heirarchy for
some reason or that distance check is wrong.
Wasn't a good idea to just skip that step though as it goes boom - though
stack trace is not useful.
Jonathan
next prev parent reply other threads:[~2022-08-17 16:17 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 2:20 [BUG] cxl can not create region Bobo WL
2022-08-08 12:37 ` Jonathan Cameron
2022-08-08 12:37 ` Jonathan Cameron via
2022-08-08 12:37 ` Jonathan Cameron via
2022-08-09 13:07 ` Bobo WL
2022-08-09 16:08 ` Jonathan Cameron
2022-08-09 16:08 ` Jonathan Cameron via
2022-08-09 16:08 ` Jonathan Cameron via
2022-08-11 17:08 ` Jonathan Cameron
2022-08-11 17:08 ` Jonathan Cameron via
2022-08-11 17:08 ` Jonathan Cameron via
2022-08-12 15:44 ` Jonathan Cameron
2022-08-12 15:44 ` Jonathan Cameron via
2022-08-12 15:44 ` Jonathan Cameron via
2022-08-12 16:03 ` Dan Williams
2022-08-12 16:15 ` Jonathan Cameron
2022-08-12 16:15 ` Jonathan Cameron via
2022-08-12 16:15 ` Jonathan Cameron via
2022-08-15 14:18 ` Jonathan Cameron
2022-08-15 14:18 ` Jonathan Cameron via
2022-08-15 14:18 ` Jonathan Cameron via
2022-08-15 14:55 ` Jonathan Cameron
2022-08-15 14:55 ` Jonathan Cameron via
2022-08-15 14:55 ` Jonathan Cameron via
2022-08-15 15:07 ` Peter Maydell
2022-08-15 17:04 ` Jonathan Cameron
2022-08-15 17:04 ` Jonathan Cameron via
2022-08-15 17:14 ` Jonathan Cameron
2022-08-15 17:14 ` Jonathan Cameron via
2022-08-15 17:14 ` Jonathan Cameron via
2022-08-15 22:55 ` Dan Williams
2022-08-17 11:25 ` Jonathan Cameron
2022-08-17 11:25 ` Jonathan Cameron via
2022-08-17 11:25 ` Jonathan Cameron via
2022-08-08 15:58 ` Dan Williams
2022-08-09 13:12 ` Bobo WL
2022-08-09 15:17 ` Dan Williams
2022-08-11 3:10 ` Bobo WL
2022-08-12 0:46 ` Dan Williams
2022-08-17 16:16 ` Jonathan Cameron [this message]
2022-08-17 16:16 ` Jonathan Cameron via
2022-08-17 16:16 ` Jonathan Cameron via
2022-08-18 16:37 ` Jonathan Cameron
2022-08-18 16:37 ` Jonathan Cameron via
2022-08-18 16:37 ` Jonathan Cameron via
2022-08-19 8:46 ` Jonathan Cameron
2022-08-19 8:46 ` Jonathan Cameron via
2022-08-19 8:46 ` Jonathan Cameron via
2022-10-10 16:20 ` Jonathan Cameron
2022-10-10 16:20 ` Jonathan Cameron via
2022-10-10 16:20 ` Jonathan Cameron via
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=20220817171619.000021ca@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=lmw.bobo@gmail.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.