- Nov 10, 2007
- 1,966
- 770
- 136
https://www.mail-archive.com/amd-gfx@lists.freedesktop.org/msg24458.html
This is an exchange between a guy trying to test NGG and having it fail. AMD contact says KMD and LLPC (drivers) are not ready and will NOT support the feature set. NGG coming in nextgen product only.
This vindicates those of us arguing that the features weren't implemented and thus the Vega chips could be faster. I also think this also adds to the leaning that Raja was let go for failure to execute. It's a huge mistake when you have a suite of features that speed things up, that could be the difference of beating or losing to competitors, that added to your cost, but they cannot be used. I'm a little disappointed to say the least.
Re: Making a GDS Allocation for NGG
Jin, Jian-Rong Wed, 15 Aug 2018 06:24:02 -0700
GFX9 will not be supported.
Thanks,
Jian-Rong Jin
在 2018年8月15日,下午8:33,Jakub Okoński <ja...@okonski.org<mailto:ja...@okonski.org>>
写道:
Hey Jian-Rong,
Will gfx9 get support from KMD and LLPC by the time gfx10 releases, or is it
only going to be a gfx10-and-forward feature?
If not, is there something missing in gfx9 hardware? Are you allowed to say?
Thanks,
Jakub
On Wed, 15 Aug 2018 at 08:36 Jin, Jian-Rong
<jian-rong....@amd.com<mailto:jian-rong....@amd.com>> wrote:
Hi Jakub。
Both KMD and LLPC are not ready to support NGG for gfx9. We are going to
support NGG in amdvlk for next generation GPU.
Thanks
Jian-Rong JIN
-----Original Message-----
From: amd-gfx
<amd-gfx-boun...@lists.freedesktop.org<mailto:amd-gfx-boun...@lists.freedesktop.org>>
On Behalf Of Jakub Okoński
Sent: 2018年8月14日 21:31
To: amd-gfx@lists.freedesktop.org<mailto:amd-gfx@lists.freedesktop.org>
Subject: Making a GDS Allocation for NGG
Hi folks,
I was trying to play around with NGG on Vega using the open source AMDVLK stack.
After fetching all the code, I disabled an override in PAL, under
gfx9SettingsLoader.cpp that disables the NGG setting. I've put a new option in
my
amdPalSettings.cfg: `NggMode,7` and that was enough to enable it.
When I ran a small vulkan application, it crashed with a "Not implemented"
error in Pal::Linux:evice::AllocateGds. The comment there says:
// TODO: implement it once amdgpu is ready.
I couldn't find anything specific to GDS allocation in upstream kernel, so I
looked at agd5f/amd-staging-drm-next and found some code related to
AMDGPU_GEM_DOMAIN_GDS and allocating a bo object. This is in
amdgpu_gem_create_ioctl, so I think it's accessible to userspace, with a small
change in libdrm, probably.
Is this what is needed to make a GDS allocation that NGG would accept, or is it
unrelated? Do you know if there are any other blockers for NGG besides this?
Regards,
Jakub
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org<mailto: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
This is an exchange between a guy trying to test NGG and having it fail. AMD contact says KMD and LLPC (drivers) are not ready and will NOT support the feature set. NGG coming in nextgen product only.
This vindicates those of us arguing that the features weren't implemented and thus the Vega chips could be faster. I also think this also adds to the leaning that Raja was let go for failure to execute. It's a huge mistake when you have a suite of features that speed things up, that could be the difference of beating or losing to competitors, that added to your cost, but they cannot be used. I'm a little disappointed to say the least.