From: patchwork-bot+netdevbpf@kernel.org
To: Jeremi Piotrowski <jpiotrowski@linux.microsoft.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
richardcochran@gmail.com, hch@lst.de
Subject: Re: [PATCH v2 RESEND] ptp: kvm: Use decrypted memory in confidential guest on x86
Date: Sat, 18 Mar 2023 05:00:18 +0000 [thread overview]
Message-ID: <167911561836.25115.1462637997047748542.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230308150531.477741-1-jpiotrowski@linux.microsoft.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 8 Mar 2023 15:05:31 +0000 you wrote:
> KVM_HC_CLOCK_PAIRING currently fails inside SEV-SNP guests because the
> guest passes an address to static data to the host. In confidential
> computing the host can't access arbitrary guest memory so handling the
> hypercall runs into an "rmpfault". To make the hypercall work, the guest
> needs to explicitly mark the memory as decrypted. Do that in
> kvm_arch_ptp_init(), but retain the previous behavior for
> non-confidential guests to save us from having to allocate memory.
>
> [...]
Here is the summary with links:
- [v2,RESEND] ptp: kvm: Use decrypted memory in confidential guest on x86
https://git.kernel.org/netdev/net-next/c/6365ba64b4db
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-03-18 5:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 15:05 [PATCH v2 RESEND] ptp: kvm: Use decrypted memory in confidential guest on x86 Jeremi Piotrowski
2023-03-17 15:59 ` Jeremi Piotrowski
2023-03-17 19:10 ` Jakub Kicinski
2023-03-18 5:00 ` patchwork-bot+netdevbpf [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=167911561836.25115.1462637997047748542.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=hch@lst.de \
--cc=jpiotrowski@linux.microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox