LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: Alex Deucher <alexdeucher@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, X86 ML <x86@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
amd-gfx@lists.freedesktop.org, Borislav Petkov <bp@alien8.de>
Subject: Re: `AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT=y` causes AMDGPU to fail on Ryzen: amdgpu: SME is not compatible with RAVEN
Date: Mon, 11 Oct 2021 15:52:14 +0200 [thread overview]
Message-ID: <139ed784-d622-b0d2-3650-736b42e624f0@molgen.mpg.de> (raw)
In-Reply-To: <87d93314-ba3e-464f-d051-84a8de674b06@amd.com>
Dear Tom,
Am 11.10.21 um 15:27 schrieb Tom Lendacky:
> On 10/11/21 8:11 AM, Borislav Petkov wrote:
>> On Mon, Oct 11, 2021 at 03:05:33PM +0200, Paul Menzel wrote:
>>> I think, the IOMMU is enabled on the MSI B350M MORTAR, but otherwise,
>>> yes
>>> this looks fine. The help text could also be updated to mention problems
>>> with AMD Raven devices.
>>
>> This is not only about Raven GPUs but, as Alex explained, pretty much
>> about every device which doesn't support a 48 bit DMA mask. I'll expand
>> that aspect in the changelog.
>
> In general, non-GPU devices that don't support a 48-bit DMA mask work
> fine (assuming they have set their DMA mask appropriately). It really
> depends on whether SWIOTLB will be able to satisfy the memory
> requirements of the driver when the IOMMU is not enabled or in
> passthrough mode. Since GPU devices need/use a lot of memory, that
> becomes a problem.
How can I check that?
Kind regards,
Paul
next prev parent reply other threads:[~2021-10-11 13:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 14:29 `AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT=y` causes AMDGPU to fail on Ryzen: amdgpu: SME is not compatible with RAVEN Paul Menzel
2021-10-05 14:38 ` Borislav Petkov
2021-10-06 6:27 ` Paul Menzel
2021-10-05 14:48 ` Alex Deucher
2021-10-06 9:42 ` Borislav Petkov
2021-10-06 13:23 ` Alex Deucher
2021-10-06 13:46 ` Borislav Petkov
2021-10-06 14:01 ` Tom Lendacky
2021-10-06 17:48 ` Borislav Petkov
2021-10-06 18:10 ` Alex Deucher
2021-10-06 18:21 ` Alex Deucher
2021-10-06 19:32 ` Borislav Petkov
2021-10-07 6:14 ` Christian König
2021-10-06 18:21 ` Borislav Petkov
2021-10-06 18:36 ` Alex Deucher
2021-10-06 19:34 ` Borislav Petkov
2021-10-06 21:39 ` Tom Lendacky
2021-10-11 13:05 ` Paul Menzel
2021-10-11 13:11 ` Borislav Petkov
2021-10-11 13:27 ` Tom Lendacky
2021-10-11 13:52 ` Paul Menzel [this message]
2021-10-11 13:58 ` Tom Lendacky
2021-10-11 14:21 ` Paul Menzel
2021-10-11 14:28 ` Tom Lendacky
2021-10-11 14:32 ` Alex Deucher
2021-10-11 16:03 ` [PATCH -v2] x86/Kconfig: Do not enable AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT automatically Borislav Petkov
2021-10-11 16:05 ` Alex Deucher
2021-10-11 16:29 ` Tom Lendacky
2021-10-11 17:18 ` [tip: x86/urgent] " tip-bot2 for Borislav Petkov
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=139ed784-d622-b0d2-3650-736b42e624f0@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).