From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Li, Xiaoyun" <xiaoyun.li@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Maslekar, Omkar" <omkar.maslekar@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] raw/ntb: add Icelake support for Intel NTB
Date: Mon, 7 Sep 2020 08:34:45 +0000 [thread overview]
Message-ID: <BN6PR11MB4052B4C5EF0C77F8AA8165A1E3280@BN6PR11MB4052.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200907022112.17640-1-xiaoyun.li@intel.com>
> +
> +static int
> +intel_ntb_dev_init(const struct rte_rawdev *dev) {
> + struct ntb_hw *hw = dev->dev_private;
> + uint8_t bar;
> + int ret, i;
> +
> + if (hw == NULL) {
> + NTB_LOG(ERR, "Invalid device.");
> + return -EINVAL;
> + }
> +
> hw->hw_addr = (char *)hw->pci_dev->mem_resource[0].addr;
>
> + if (is_gen3_ntb(hw)) {
> + ret = intel_ntb3_check_ppd(hw);
> + } else if (is_gen4_ntb(hw)) {
> + /* PPD is in MMIO but not config space for NTB Gen4 */
> + ret = intel_ntb4_check_ppd(hw);
> + if (ret)
> + return ret;
Above two lines are not necessary.
> + } else {
> + return -ENOTSUP;
> + }
> +
> + if (ret)
> + return ret;
> +
> hw->mw_cnt = XEON_MW_COUNT;
> hw->db_cnt = XEON_DB_COUNT;
> hw->spad_cnt = XEON_SPAD_COUNT;
> @@ -149,15 +219,28 @@ intel_ntb_mw_set_trans(const struct rte_rawdev
> *dev, int mw_idx,
> rte_write64(base, xlat_addr);
> rte_write64(limit, limit_addr);
>
> - /* Setup the external point so that remote can access. */
> - xlat_off = XEON_EMBAR1_OFFSET + 8 * mw_idx;
> - xlat_addr = hw->hw_addr + xlat_off;
> - limit_off = XEON_EMBAR1XLMT_OFFSET + mw_idx *
> XEON_BAR_INTERVAL_OFFSET;
> - limit_addr = hw->hw_addr + limit_off;
> - base = rte_read64(xlat_addr);
> - base &= ~0xf;
> - limit = base + size;
> - rte_write64(limit, limit_addr);
> + if (is_gen3_ntb(hw)) {
> + /* Setup the external point so that remote can access. */
> + xlat_off = XEON_EMBAR1_OFFSET + 8 * mw_idx;
> + xlat_addr = hw->hw_addr + xlat_off;
> + limit_off = XEON_EMBAR1XLMT_OFFSET +
> + mw_idx * XEON_BAR_INTERVAL_OFFSET;
> + limit_addr = hw->hw_addr + limit_off;
> + base = rte_read64(xlat_addr);
> + base &= ~0xf;
> + limit = base + size;
> + rte_write64(limit, limit_addr);
> + } else if (is_gen4_ntb(hw)) {
Can we use a variable in struct to indicate it's gen4 or gen3 after init instead of check it every time?
> + /* Set translate base address index register */
> + xlat_off = XEON_GEN4_IM1XBASEIDX_OFFSET +
> + mw_idx * XEON_GEN4_XBASEIDX_INTERVAL;
> + xlat_addr = hw->hw_addr + xlat_off;
> + rte_write16(rte_log2_u64(size), xlat_addr);
> + } else {
> + rte_write64(base, limit_addr);
> + rte_write64(0, xlat_addr);
> + return -ENOTSUP;
> + }
Is the else branch necessary? As if neither gen3 or gen4, the init would fail. Would be better to print an ERR instead of just return NO support.
>
> return 0;
> }
next prev parent reply other threads:[~2020-09-07 8:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 4:59 [dpdk-dev] [PATCH] " Xiaoyun Li
2020-09-07 1:46 ` [dpdk-dev] [PATCH v2] " Xiaoyun Li
2020-09-07 2:21 ` [dpdk-dev] [PATCH v3] " Xiaoyun Li
2020-09-07 8:34 ` Wu, Jingjing [this message]
2020-09-07 9:18 ` Li, Xiaoyun
2020-09-07 16:15 ` Wu, Jingjing
2020-09-08 1:53 ` Li, Xiaoyun
2020-09-08 3:27 ` [dpdk-dev] [PATCH v4] raw/ntb: add Ice Lake " Xiaoyun Li
2020-09-08 4:43 ` Wu, Jingjing
2020-10-05 23:25 ` Thomas Monjalon
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=BN6PR11MB4052B4C5EF0C77F8AA8165A1E3280@BN6PR11MB4052.namprd11.prod.outlook.com \
--to=jingjing.wu@intel.com \
--cc=dev@dpdk.org \
--cc=omkar.maslekar@intel.com \
--cc=xiaoyun.li@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;
as well as URLs for NNTP newsgroup(s).