From: Sam Bobroff <sbobroff@linux.ibm.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Alex Williamson <alex.williamson@redhat.com>,
linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org
Subject: Re: [PATCH 1/1] vfio-pci/nvlink2: Allow fallback to ibm,mmio-atsd[0]
Date: Fri, 7 Feb 2020 13:39:15 +1100 [thread overview]
Message-ID: <20200207023914.GC21238@osmium> (raw)
In-Reply-To: <84147d70-3409-e216-495d-fc54366b92a6@ozlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 2363 bytes --]
On Thu, Feb 06, 2020 at 03:23:03PM +1100, Alexey Kardashevskiy wrote:
>
>
> On 06/02/2020 14:17, Sam Bobroff wrote:
> > Older versions of skiboot only provide a single value in the device
> > tree property "ibm,mmio-atsd", even when multiple Address Translation
> > Shoot Down (ATSD) registers are present. This prevents NVLink2 devices
> > (other than the first) from being used with vfio-pci because vfio-pci
> > expects to be able to assign a dedicated ATSD register to each NVLink2
> > device.
> >
> > However, ATSD registers can be shared among devices. This change
> > allows vfio-pci to fall back to sharing the register at index 0 if
> > necessary.
> >
> > Signed-off-by: Sam Bobroff <sbobroff@linux.ibm.com>
> > ---
> > drivers/vfio/pci/vfio_pci_nvlink2.c | 13 +++++++++++--
> > 1 file changed, 11 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/vfio/pci/vfio_pci_nvlink2.c b/drivers/vfio/pci/vfio_pci_nvlink2.c
> > index f2983f0f84be..851ba673882b 100644
> > --- a/drivers/vfio/pci/vfio_pci_nvlink2.c
> > +++ b/drivers/vfio/pci/vfio_pci_nvlink2.c
> > @@ -420,8 +420,17 @@ int vfio_pci_ibm_npu2_init(struct vfio_pci_device *vdev)
> >
> > if (of_property_read_u64_index(hose->dn, "ibm,mmio-atsd", nvlink_index,
> > &mmio_atsd)) {
> > - dev_warn(&vdev->pdev->dev, "No available ATSD found\n");
> > - mmio_atsd = 0;
> > + dev_warn(&vdev->pdev->dev,
> > + "No ibm,mmio-atsd[%d] found: trying ibm,mmio-atsd[0]\n",
> > + nvlink_index);
>
>
> We do not really need this warning (nvlink_index doesn't matter that
> much, we can work out from the device tree what happened), warnings
> below are enough (if you really want, you can print nvlink_index there).
>
> Either way,
>
> Reviewed-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>
Thanks,
I'll change it if there's some reason to do another version but
otherwise leave it as is.
Sam.
>
>
>
> > + if (of_property_read_u64_index(hose->dn, "ibm,mmio-atsd", 0,
> > + &mmio_atsd)) {
> > + dev_warn(&vdev->pdev->dev, "No available ATSD found\n");
> > + mmio_atsd = 0;
> > + } else {
> > + dev_warn(&vdev->pdev->dev,
> > + "Using fallback ibm,mmio-atsd[0] for ATSD.\n");
> > + }
> > }
> >
> > if (of_property_read_u64(npu_node, "ibm,device-tgt-addr", &tgt)) {
> >
>
> --
> Alexey
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Sam Bobroff <sbobroff@linux.ibm.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: kvm@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [PATCH 1/1] vfio-pci/nvlink2: Allow fallback to ibm,mmio-atsd[0]
Date: Fri, 7 Feb 2020 13:39:15 +1100 [thread overview]
Message-ID: <20200207023914.GC21238@osmium> (raw)
In-Reply-To: <84147d70-3409-e216-495d-fc54366b92a6@ozlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 2363 bytes --]
On Thu, Feb 06, 2020 at 03:23:03PM +1100, Alexey Kardashevskiy wrote:
>
>
> On 06/02/2020 14:17, Sam Bobroff wrote:
> > Older versions of skiboot only provide a single value in the device
> > tree property "ibm,mmio-atsd", even when multiple Address Translation
> > Shoot Down (ATSD) registers are present. This prevents NVLink2 devices
> > (other than the first) from being used with vfio-pci because vfio-pci
> > expects to be able to assign a dedicated ATSD register to each NVLink2
> > device.
> >
> > However, ATSD registers can be shared among devices. This change
> > allows vfio-pci to fall back to sharing the register at index 0 if
> > necessary.
> >
> > Signed-off-by: Sam Bobroff <sbobroff@linux.ibm.com>
> > ---
> > drivers/vfio/pci/vfio_pci_nvlink2.c | 13 +++++++++++--
> > 1 file changed, 11 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/vfio/pci/vfio_pci_nvlink2.c b/drivers/vfio/pci/vfio_pci_nvlink2.c
> > index f2983f0f84be..851ba673882b 100644
> > --- a/drivers/vfio/pci/vfio_pci_nvlink2.c
> > +++ b/drivers/vfio/pci/vfio_pci_nvlink2.c
> > @@ -420,8 +420,17 @@ int vfio_pci_ibm_npu2_init(struct vfio_pci_device *vdev)
> >
> > if (of_property_read_u64_index(hose->dn, "ibm,mmio-atsd", nvlink_index,
> > &mmio_atsd)) {
> > - dev_warn(&vdev->pdev->dev, "No available ATSD found\n");
> > - mmio_atsd = 0;
> > + dev_warn(&vdev->pdev->dev,
> > + "No ibm,mmio-atsd[%d] found: trying ibm,mmio-atsd[0]\n",
> > + nvlink_index);
>
>
> We do not really need this warning (nvlink_index doesn't matter that
> much, we can work out from the device tree what happened), warnings
> below are enough (if you really want, you can print nvlink_index there).
>
> Either way,
>
> Reviewed-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>
Thanks,
I'll change it if there's some reason to do another version but
otherwise leave it as is.
Sam.
>
>
>
> > + if (of_property_read_u64_index(hose->dn, "ibm,mmio-atsd", 0,
> > + &mmio_atsd)) {
> > + dev_warn(&vdev->pdev->dev, "No available ATSD found\n");
> > + mmio_atsd = 0;
> > + } else {
> > + dev_warn(&vdev->pdev->dev,
> > + "Using fallback ibm,mmio-atsd[0] for ATSD.\n");
> > + }
> > }
> >
> > if (of_property_read_u64(npu_node, "ibm,device-tgt-addr", &tgt)) {
> >
>
> --
> Alexey
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-07 2:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 3:17 [PATCH 1/1] vfio-pci/nvlink2: Allow fallback to ibm,mmio-atsd[0] Sam Bobroff
2020-02-06 4:23 ` Alexey Kardashevskiy
2020-02-07 2:39 ` Sam Bobroff [this message]
2020-02-07 2:39 ` Sam Bobroff
2020-02-07 4:43 ` Sam Bobroff
2020-02-07 4:43 ` Sam Bobroff
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=20200207023914.GC21238@osmium \
--to=sbobroff@linux.ibm.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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.