From: bugzilla-daemon@bugzilla.kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 211117] dma_mmap_coherent() - garbage sound output with mem_encrypt on Ryzen platform
Date: Tue, 19 Jan 2021 19:33:00 +0000 [thread overview]
Message-ID: <bug-211117-215701-Am6NIQ8Vem@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211117-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=211117
thomas.lendacky@amd.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |thomas.lendacky@amd.com
--- Comment #17 from thomas.lendacky@amd.com ---
This sounds like a mismatch between the encryption bit in the kernel and the
encryption bit in userspace. It looks like that should be taken care of by the
dma_pgprot() call in dma_mmap_attrs() or in iommu_dma_mmap(). But maybe the
force_dma_unencrypted() in arch/x86/mm/mem_encrypt.c needs to understand if the
IOMMU is doing the mapping. Since, even if the device doesn't support 48-bit or
higher DMA, it will still done encrypted because of the IOMMU. I don't see any
dmesg output, is the IOMMU enabled? What happens if you do iommu=pt on the
kernel command line?
Alternatively, if you want memory encryption for your bare-metal system, you
can see if the BIOS supports TSME (Transparent SME). Then you can remove
mem_encrypt=on or add mem_encrypt=off (if enabled by default), and still get
memory encryption.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-01-19 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-211117-215701@https.bugzilla.kernel.org/>
2021-01-18 14:27 ` [Bug 211117] [oxygen] [virtuoso] route, dmix and other alsa plugins produce garbage output with mem_encrypt on Ryzen platform bugzilla-daemon
2021-01-18 14:28 ` [Bug 211117] dma_mmap_coherent() - garbage sound " bugzilla-daemon
2021-01-18 14:36 ` bugzilla-daemon
2021-01-19 19:33 ` bugzilla-daemon [this message]
2021-01-20 12:47 ` bugzilla-daemon
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=bug-211117-215701-Am6NIQ8Vem@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=platform-driver-x86@vger.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