From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: "Xingtao Yao (Fujitsu)" <yaoxt.fnst@fujitsu.com>
Cc: "dave@stgolabs.net" <dave@stgolabs.net>,
"dave.jiang@intel.com" <dave.jiang@intel.com>,
"alison.schofield@intel.com" <alison.schofield@intel.com>,
"vishal.l.verma@intel.com" <vishal.l.verma@intel.com>,
"ira.weiny@intel.com" <ira.weiny@intel.com>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"jim.harris@samsung.com" <jim.harris@samsung.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH v5] cxl/region: check interleave capability
Date: Mon, 10 Jun 2024 11:25:36 +0100 [thread overview]
Message-ID: <20240610112536.0000003e@Huawei.com> (raw)
In-Reply-To: <OSZPR01MB6453B7063C3425B8824EDEA38DFA2@OSZPR01MB6453.jpnprd01.prod.outlook.com>
> >
> > > + * interleave bits is 0, there is no interleaving, the following
> > > + * check is ignored.
> >
> > If the interleave is 3 there is no interleave? That seems an odd statement
> > perhaps make that comment more detailed.
> > My understanding is that it's just more complex and all bits are relevant.
> yes, but it is difficult to describe the interleave bits.
> In the SPCE " 8.2.4.20.13 Decoder Protection ", only when IW < 8, it called
> [IG + IW +7: IG+8] as IW bits.
> but when IW >= 8, what is the IW bits definition?
>
> In my opinion:
> if IW = 8, all the bits of HPAOFFSET[51:0] is used, so the IW bits is none.
> if IW >8, the bits [IG+IW-1: IG+8] of HPAOFFSET is not used, so the IW bits should be [IG+IW-1: IG+8],
I'd just add a note that things are more complex for multiples of 3 and
drop the 'no interleave' comment.
It's an early validation function to give more useful feedback than
the current no feedback. I'm not sure it needs to be perfect in catching
issues as long as we don't think it will give false rejections of valid
parameters.
next prev parent reply other threads:[~2024-06-10 10:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 9:27 [PATCH v5] cxl/region: check interleave capability Yao Xingtao
2024-06-05 13:16 ` Jonathan Cameron
2024-06-06 2:19 ` Xingtao Yao (Fujitsu)
2024-06-10 10:25 ` Jonathan Cameron [this message]
2024-06-05 15:55 ` Alison Schofield
2024-06-06 3:46 ` Xingtao Yao (Fujitsu)
2024-06-10 10:36 ` Jonathan Cameron
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=20240610112536.0000003e@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=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=jim.harris@samsung.com \
--cc=linux-cxl@vger.kernel.org \
--cc=vishal.l.verma@intel.com \
--cc=yaoxt.fnst@fujitsu.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