All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Kuehling <felix.kuehling@amd.com>
To: Daniel Phillips <daniel.phillips@amd.com>,
	amd-gfx@lists.freedesktop.org,  dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/1] Add test for hsaKmtAvailableMemory available memory inquiry
Date: Mon, 10 Jan 2022 18:46:52 -0500	[thread overview]
Message-ID: <8c93c26b-df12-6c73-5f52-5ff717bb61da@amd.com> (raw)
In-Reply-To: <20220110214822.3175297-1-daniel.phillips@amd.com>

On 2022-01-10 4:48 p.m., Daniel Phillips wrote:
> Basic test for the new hsaKmtAvailableMemory library call. This is
> a standalone test, does not modify any of the other tests just to
> be on the safe side. More elaborate tests coming soon.
>
> Change-Id: I738600d4b74cc5dba6b857e4c793f6b14b7d2283
> Signed-off-by: Daniel Phillips <daniel.phillips@amd.com>
> ---
>   tests/kfdtest/src/KFDMemoryTest.cpp | 17 +++++++++++++++++
>   1 file changed, 17 insertions(+)
>
> diff --git a/tests/kfdtest/src/KFDMemoryTest.cpp b/tests/kfdtest/src/KFDMemoryTest.cpp
> index 9f62727..1f93928 100644
> --- a/tests/kfdtest/src/KFDMemoryTest.cpp
> +++ b/tests/kfdtest/src/KFDMemoryTest.cpp
> @@ -595,6 +595,23 @@ TEST_F(KFDMemoryTest, MemoryAlloc) {
>       TEST_END
>   }
>   
> +// Basic test for hsaKmtAllocMemory
> +TEST_F(KFDMemoryTest, MemoryAllocAll) {
> +    TEST_START(TESTPROFILE_RUNALL)
> +
> +    unsigned int* pBig = NULL;
> +    unsigned int* pSmall = NULL;
> +    m_MemoryFlags.ui32.NoNUMABind = 1;
> +    HSAuint64 available;
> +    EXPECT_SUCCESS(hsaKmtAvailableMemory(0 /* system */, &available));
I don't think you've even implemented this API for system memory. The 
system memory node doesn't have a valid GPUID, so the ioctl will fail.

I'd expect this test to work only for VRAM.


> +    EXPECT_SUCCESS(hsaKmtAllocMemory(0 /* system */, available, m_MemoryFlags, reinterpret_cast<void**>(&pBig)));
> +    EXPECT_NE(HSAKMT_STATUS_SUCCESS, hsaKmtAllocMemory(0 /* system */, PAGE_SIZE, m_MemoryFlags, reinterpret_cast<void**>(&pSmall)));
> +    EXPECT_SUCCESS(hsaKmtFreeMemory(pBig, available));
> +    EXPECT_SUCCESS(hsaKmtAllocMemory(0 /* system */, PAGE_SIZE, m_MemoryFlags, reinterpret_cast<void**>(&pSmall)));

You're leaking pSmall here.

Regards,
   Felix


> +
> +    TEST_END
> +}
> +
>   TEST_F(KFDMemoryTest, AccessPPRMem) {
>       TEST_START(TESTPROFILE_RUNALL)
>   

      reply	other threads:[~2022-01-10 23:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 21:48 [PATCH 1/1] Add test for hsaKmtAvailableMemory available memory inquiry Daniel Phillips
2022-01-10 23:46 ` 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=8c93c26b-df12-6c73-5f52-5ff717bb61da@amd.com \
    --to=felix.kuehling@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=daniel.phillips@amd.com \
    --cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.