From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Oliver O'Halloran" <oohall@gmail.com>
Cc: Oded Gabbay <oded.gabbay@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
linuxppc-dev@ozlabs.org, Christoph Hellwig <hch@infradead.org>,
Russell Currey <ruscur@au1.ibm.com>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 8/8] habanalabs: enable 64-bit DMA mask in POWER9
Date: Wed, 12 Jun 2019 18:17:46 +1000 [thread overview]
Message-ID: <ff34090039ba2ce880a74b0a3714c8ed38f64ed7.camel@kernel.crashing.org> (raw)
In-Reply-To: <CAOSf1CFcYnhKf0EJkm+E5uHg4e=QYGe+vAUz_TjX-v6UsmNtFA@mail.gmail.com>
On Wed, 2019-06-12 at 15:45 +1000, Oliver O'Halloran wrote:
>
> Also, are you sure about the MSI thing? The IODA3 spec says the only
> important bits for a 64bit MSI are bits 61:60 (to hit the window) and
> the lower bits that determine what IVE to use. Everything in between
> is ignored so ORing in bit 59 shouldn't break anything.
On IODA3... could be different on another system. My point is you can't
just have a fixed setting for all top bits for DMA & MSIs.
> > This will only work as long as all of the system memory can be
> > addressed at an offset from that fixed address that itself fits your
> > device addressing capabilities (50 bits in this case). It may or may
> > not be the case but there's no way to check since the DMA mask logic
> > won't really apply.
> >
> > You might want to consider fixing your HW in the next iteration... This
> > is going to bite you when x86 increases the max physical memory for
> > example, or on other architectures.
>
> Yes, do this. The easiest way to avoid this sort of wierd hack is to
> just design the PCIe interface to the spec in the first place.
Ben.
next prev parent reply other threads:[~2019-06-12 8:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 9:21 [PATCH v2 8/8] habanalabs: enable 64-bit DMA mask in POWER9 Oded Gabbay
2019-06-11 9:58 ` Greg KH
2019-06-11 11:47 ` Oded Gabbay
2019-06-11 15:17 ` Christoph Hellwig
2019-06-11 15:26 ` Greg KH
2019-06-11 17:03 ` Oded Gabbay
2019-06-11 17:22 ` Oded Gabbay
2019-06-11 22:53 ` Benjamin Herrenschmidt
2019-06-12 5:45 ` Oliver O'Halloran
2019-06-12 8:17 ` Benjamin Herrenschmidt [this message]
2019-06-12 6:25 ` Oded Gabbay
2019-06-12 8:18 ` Benjamin Herrenschmidt
2019-06-12 6:35 ` Oliver O'Halloran
2019-06-12 6:53 ` Christoph Hellwig
2019-06-12 11:48 ` Oliver O'Halloran
2019-06-15 12:12 ` Oded Gabbay
2019-06-16 9:55 ` Christoph Hellwig
2019-06-16 11:24 ` Oded Gabbay
2019-06-17 8:19 ` Christoph Hellwig
2019-06-17 8:35 ` Oded Gabbay
2019-06-24 6:53 ` Oded Gabbay
2019-06-24 6:58 ` Christoph Hellwig
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=ff34090039ba2ce880a74b0a3714c8ed38f64ed7.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=oded.gabbay@gmail.com \
--cc=oohall@gmail.com \
--cc=ruscur@au1.ibm.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