From: Klaus Jensen <its@irrelevant.dk>
To: Keith Busch <kbusch@kernel.org>
Cc: Jens Axboe <axboe@fb.com>, Klaus Jensen <k.jensen@samsung.com>,
Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org, Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH] nvme: allow use of cmb on v1.4 controllers
Date: Fri, 15 Jan 2021 07:13:11 +0100 [thread overview]
Message-ID: <YAEyd5fNOa1/3gN2@apples.localdomain> (raw)
In-Reply-To: <20210114180600.GA1511435@dhcp-10-100-145-180.wdc.com>
[-- Attachment #1.1: Type: text/plain, Size: 1656 bytes --]
On Jan 14 10:06, Keith Busch wrote:
> On Thu, Jan 14, 2021 at 02:24:41PM +0100, Klaus Jensen wrote:
> > @@ -1795,6 +1796,15 @@ static void nvme_map_cmb(struct nvme_dev *dev)
> > if (dev->cmb_size)
> > return;
> >
> > + vs = readl(dev->bar + NVME_REG_VS);
> > +
> > + if (vs >= NVME_VS(1, 4, 0)) {
> > + if (!NVME_CAP_CMBS(dev->ctrl.cap))
> > + return;
> > +
> > + writel(NVME_CMBMSC_CRE, dev->bar + NVME_REG_CMBMSC);
> > + }
> > +
> > dev->cmbsz = readl(dev->bar + NVME_REG_CMBSZ);
> > if (!dev->cmbsz)
> > return;
> > @@ -1805,6 +1815,19 @@ static void nvme_map_cmb(struct nvme_dev *dev)
> > bar = NVME_CMB_BIR(dev->cmbloc);
> > bar_size = pci_resource_len(pdev, bar);
> >
> > + if (vs >= NVME_VS(1, 4, 0)) {
> > + cmbmsc = pci_resource_start(pdev, bar);
>
> Shouldn't this have a '+ offset' in case the CMB doesn't start at the
> beginning of the bar?
>
Of course, good catch!
> > + cmbmsc |= (NVME_CMBMSC_CRE | NVME_CMBMSC_CMSE);
> > +
> > + /*
> > + * Writing the low bits may cause the controller to check the
> > + * validity of the 52 bit controller base address in the CMBMSC
> > + * register, so write the high bits first.
> > + */
> > + writel(cmbmsc >> 32, dev->bar + NVME_REG_CMBMSC + 4);
> > + writel(cmbmsc, dev->bar + NVME_REG_CMBMSC);
>
> hi_lo_writeq()?
>
Ah, was looking for that...
> This should probably come after we've verified the '(offset > bar_size)'
> check below so that we're not enabling these capabilities before we know
> if they're within the BAR.
>
Right.
> > + }
> > +
> > if (offset > bar_size)
> > return;
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 158 bytes --]
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2021-01-15 6:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 13:24 [PATCH] nvme: allow use of cmb on v1.4 controllers Klaus Jensen
2021-01-14 17:33 ` Christoph Hellwig
2021-01-15 6:12 ` Klaus Jensen
2021-01-14 18:06 ` Keith Busch
2021-01-14 18:15 ` Keith Busch
2021-01-15 6:13 ` Klaus Jensen [this message]
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=YAEyd5fNOa1/3gN2@apples.localdomain \
--to=its@irrelevant.dk \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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