dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Timur Kristóf" <timur.kristof@gmail.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: michael.jamet@intel.com, dri-devel@lists.freedesktop.org
Subject: Re: Missing Thunderbolt 3 PCI-E atomics support
Date: Thu, 14 Mar 2019 18:26:00 +0100	[thread overview]
Message-ID: <14bb183e6de7fb324954c56e9cae91391f8d7f4c.camel@gmail.com> (raw)
In-Reply-To: <20190314103043.GG2588@lahna.fi.intel.com>

On Thu, 2019-03-14 at 12:30 +0200, Mika Westerberg wrote:
> On Wed, Mar 13, 2019 at 07:09:26PM +0100, Timur Kristóf wrote:
> > Hi,
> 
> Hi,
> 
> > I was sent here by Greg KH from the Linux USB mailing list, I hope
> > this
> > is the right place to ask.
> > 
> > PCI-E atomics don't work for me with Thunderbolt 3.
> > I see the following message from my Thunderbolt 3 eGPU in dmesg:
> > 
> > kfd: skipped device 1002:67df, PCI rejects atomics
> > 
> > Hardware is a Dell XPS 13 9370 (with i7-8550U CPU) connected to a
> > Zotac
> > AMP mini, with an AMD RX 570 graphics card. Due to this, I cannot
> > use
> > the GPU for OpenCL, because the compute stack requires PCI-E
> > atomics
> > support [1].
> > 
> > What could be the problem? Is this a hardware limitation or a
> > missing
> > feature in the Linux TB driver?
> 
> I don't think it has anything to do with TBT itself. AtomicOps is a
> PCIe
> feature.
> 
> What does 'sudo lspci -vv' show for the ports in question?

Hi Mika,

I know atomics is a PCIe feature, but in this case the PCIe goes
through TB3, so I would assume it has something to do with it.

Here is the output of 'lspci -vv':
https://pastebin.com/Qt5RUFVc

Best regards,
Tim


_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-03-14 17:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 18:09 Missing Thunderbolt 3 PCI-E atomics support Timur Kristóf
2019-03-14 10:30 ` Mika Westerberg
2019-03-14 17:26   ` Timur Kristóf [this message]
2019-03-14 17:40     ` Mika Westerberg
2019-03-14 17:54       ` Timur Kristóf
2019-03-14 18:17         ` Mika Westerberg
2019-03-14 18:36           ` Timur Kristóf
2019-03-15 19:46             ` Dieter Nützel
2019-03-15 20:03               ` Alex Deucher

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=14bb183e6de7fb324954c56e9cae91391f8d7f4c.camel@gmail.com \
    --to=timur.kristof@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=michael.jamet@intel.com \
    --cc=mika.westerberg@linux.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