From: Shamir Rabinovitch <shamir.rabinovitch-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH v1] net/mlx4_core: VF probe fail when HW support 64-bit coherent DMA
Date: Sun, 8 Jan 2017 17:08:39 +0200 [thread overview]
Message-ID: <20170108150838.GA2106@shamir-linux.uk.oracle.com> (raw)
In-Reply-To: <20170108143032.GA22478-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
On Sun, Jan 08, 2017 at 06:30:32AM -0800, Christoph Hellwig wrote:
> On Sun, Jan 08, 2017 at 04:14:49AM -0500, Shamir Rabinovitch wrote:
> > CX3 firmware is unable to work with 64-bit coherent DMA. If IOMMU
> > support 64-bit coherent DMA mlx4_core driver will try to use it
> > and VF probe will fail due to firmware error.
> >
> > Force all mlx4_core coherent DMA to 32-bit only!
>
> If this is only an issue with VFs it should be limited to VF PCI IDs.
> If not the changelog should be updated a bit.
Agree. Thanks for the comment.
I will do that once Mellanox review the patch and say how wide is
this issue. Is this issue limited to specific Mellanox firmware ? Is
this issue limited to specific HW ? I have asked Mellanox all those
question via our support channel and still have not got any answers.
BR, Shamir
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-01-08 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 9:14 [PATCH v1] net/mlx4_core: VF probe fail when HW support 64-bit coherent DMA Shamir Rabinovitch
[not found] ` <1483866889-10700-1-git-send-email-shamir.rabinovitch-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-01-08 14:30 ` Christoph Hellwig
[not found] ` <20170108143032.GA22478-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-01-08 15:08 ` Shamir Rabinovitch [this message]
[not found] ` <20170108150838.GA2106-wNzywhU3BCWJbeQQAEUYZUB3C2bhBk7L0E9HWUfgJXw@public.gmane.org>
2017-01-09 6:51 ` Leon Romanovsky
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=20170108150838.GA2106@shamir-linux.uk.oracle.com \
--to=shamir.rabinovitch-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox