All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: Christoph Hellwig <hch@infradead.org>, iommu@lists.linux-foundation.org
Subject: Memory clearing in swiotlb_update_mem_attributes()
Date: Wed, 5 Jan 2022 01:49:39 +0300	[thread overview]
Message-ID: <20220104224939.yhpceiuzqqhb72ql@box.shutemov.name> (raw)

Hi Tom,

For larger TDX VM, memset() after set_memory_decrypted() in
swiotlb_update_mem_attributes() takes substantial portion of boot time.

It makes me wounder why do we need it there? Malicious VMM can mess with
decrypted/shared buffer at any point and for normal use it will be
populated with real data anyway.

Can we drop it?

-- 
 Kirill A. Shutemov
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

             reply	other threads:[~2022-01-04 22:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 22:49 Kirill A. Shutemov [this message]
2022-01-05 14:06 ` Memory clearing in swiotlb_update_mem_attributes() Tom Lendacky via iommu
2022-01-05 14:12   ` Christoph Hellwig
2022-01-05 15:58     ` Kirill A. Shutemov
2022-01-10 15:58   ` Tom Lendacky via iommu

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=20220104224939.yhpceiuzqqhb72ql@box.shutemov.name \
    --to=kirill@shutemov.name \
    --cc=hch@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=thomas.lendacky@amd.com \
    /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.