public inbox for amd-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Felix Kuehling <felix.kuehling-5C7GfCeVMHo@public.gmane.org>
To: Alexander Frolov <frolov-4PKdL1x4DgGHXe+LvDLADg@public.gmane.org>,
	amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: kfdtest failures for amdkfd (amd-staging-drm-next)
Date: Fri, 14 Sep 2018 17:40:53 -0400	[thread overview]
Message-ID: <6abb2acf-bf4a-6431-59da-21dec689efdb@amd.com> (raw)
In-Reply-To: <37f71cd7-364e-c951-0e70-8d0d7b17f5e1-4PKdL1x4DgGHXe+LvDLADg@public.gmane.org>

You need ROCm 1.9 to work with the upstream KFD. libhsakmt from ROCm 1.8
is incompatible with the upstream KFD ABI.

Where did you get KFDTest? It's part of the same repository on GitHub as
libhsakmt. It's new on the 1.9 branch. You need libhsakmt from the same
branch. The ROCm 1.9 binaries are planned to be released later today if
all goes well.

Regards,
  Felix


On 2018-09-14 07:50 AM, Alexander Frolov wrote:
> Hi!
>
> I am trying to use amd-staging-drm-next to work with amdkfd (built
> into amdgpu) for the AMD Instinct MI25 device.
>
> As a first step I compiled libhsakmt 1.8.x and tried to run kfdtest.
> But it produces lots of failures (see below).
> Here are the results:
>
> ...
> [==========] 76 tests from 14 test cases ran. (80250 ms total)
> [  PASSED  ] 39 tests.
> [  FAILED  ] 37 tests, listed below:
> [  FAILED  ] KFDEvictTest.QueueTest
> [  FAILED  ] KFDGraphicsInterop.RegisterGraphicsHandle
> [  FAILED  ] KFDIPCTest.BasicTest
> [  FAILED  ] KFDIPCTest.CrossMemoryAttachTest
> [  FAILED  ] KFDIPCTest.CMABasicTest
> [  FAILED  ] KFDLocalMemoryTest.BasicTest
> [  FAILED  ] KFDLocalMemoryTest.VerifyContentsAfterUnmapAndMap
> [  FAILED  ] KFDLocalMemoryTest.CheckZeroInitializationVram
> [  FAILED  ] KFDMemoryTest.MapUnmapToNodes
> [  FAILED  ] KFDMemoryTest.MemoryRegisterSamePtr
> [  FAILED  ] KFDMemoryTest.FlatScratchAccess
> [  FAILED  ] KFDMemoryTest.MMBench
> [  FAILED  ] KFDMemoryTest.QueryPointerInfo
> [  FAILED  ] KFDMemoryTest.PtraceAccessInvisibleVram
> [  FAILED  ] KFDMemoryTest.SignalHandling
> [  FAILED  ] KFDQMTest.CreateCpQueue
> [  FAILED  ] KFDQMTest.CreateMultipleSdmaQueues
> [  FAILED  ] KFDQMTest.SdmaConcurrentCopies
> [  FAILED  ] KFDQMTest.CreateMultipleCpQueues
> [  FAILED  ] KFDQMTest.DisableSdmaQueueByUpdateWithNullAddress
> [  FAILED  ] KFDQMTest.DisableCpQueueByUpdateWithZeroPercentage
> [  FAILED  ] KFDQMTest.OverSubscribeCpQueues
> [  FAILED  ] KFDQMTest.BasicCuMaskingEven
> [  FAILED  ] KFDQMTest.QueuePriorityOnDifferentPipe
> [  FAILED  ] KFDQMTest.QueuePriorityOnSamePipe
> [  FAILED  ] KFDQMTest.EmptyDispatch
> [  FAILED  ] KFDQMTest.SimpleWriteDispatch
> [  FAILED  ] KFDQMTest.MultipleCpQueuesStressDispatch
> [  FAILED  ] KFDQMTest.CpuWriteCoherence
> [  FAILED  ] KFDQMTest.CreateAqlCpQueue
> [  FAILED  ] KFDQMTest.QueueLatency
> [  FAILED  ] KFDQMTest.CpQueueWraparound
> [  FAILED  ] KFDQMTest.SdmaQueueWraparound
> [  FAILED  ] KFDQMTest.Atomics
> [  FAILED  ] KFDQMTest.P2PTest
> [  FAILED  ] KFDQMTest.SdmaEventInterrupt
> [  FAILED  ] KFDTopologyTest.BasicTest
>
> Does it mean that current amdkfd from the kernel cant be used with
> libhsakmt 1.8.x? or I am doing something wrong...
> Thank you!
>
> Best,
>    Alexander
>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

      parent reply	other threads:[~2018-09-14 21:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-14 11:50 kfdtest failures for amdkfd (amd-staging-drm-next) Alexander Frolov
     [not found] ` <37f71cd7-364e-c951-0e70-8d0d7b17f5e1-4PKdL1x4DgGHXe+LvDLADg@public.gmane.org>
2018-09-14 21:40   ` Felix Kuehling [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=6abb2acf-bf4a-6431-59da-21dec689efdb@amd.com \
    --to=felix.kuehling-5c7gfcevmho@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=frolov-4PKdL1x4DgGHXe+LvDLADg@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