public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nikunj A. Dadhania" <nikunj@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: thomas.lendacky@amd.com, x86@kernel.org, dionnaglaze@google.com,
	pgonda@google.com, seanjc@google.com, pbonzini@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 00/14] Add Secure TSC support for SNP guests
Date: Thu, 5 Oct 2023 19:27:43 +0530	[thread overview]
Message-ID: <1f740bdd-666b-4686-8d04-1c28da9917bd@amd.com> (raw)
In-Reply-To: <20231004070100.GAZR0NrFSIDKPSQIjA@fat_crate.local>

On 10/4/2023 12:31 PM, Borislav Petkov wrote:
> On Wed, Oct 04, 2023 at 11:05:14AM +0530, Nikunj A. Dadhania wrote:
>> On 8/28/2023 9:17 AM, Nikunj A. Dadhania wrote:
>>> On 8/14/2023 11:22 AM, Nikunj A Dadhania wrote:
>>>> Secure TSC allows guests to securely use RDTSC/RDTSCP instructions as the
>>>> parameters being used cannot be changed by hypervisor once the guest is
>>>> launched. More details in the AMD64 APM Vol 2, Section "Secure TSC".
>>>>
>> ...
>>>>
>>>> Changelog:
>>>> ----------
>>>> v4:
>>>> * Drop handle_guest_request() and handle_guest_request_ext()
>>>> * Drop NULL check for key
>>>> * Corrected commit subject
>>>> * Added Reviewed-by from Tom
>>>
>>> A gentle reminder.
>>
>>
>> Ping ?
> 
> Pong.
> 
> How about you find other SEV patches on LKML which are waiting for
> review and review them, while waiting for yours?

That is a good idea and I wasn't aware that this may work as a good bribe [1] :-)

Regards,
Nikunj

[1] https://lore.kernel.org/all/20230816081942.GBZNyGnk%2FK+nDuBzsC@fat_crate.local/


  reply	other threads:[~2023-10-05 14:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14  5:52 [PATCH v4 00/14] Add Secure TSC support for SNP guests Nikunj A Dadhania
2023-08-14  5:52 ` [PATCH v4 01/14] virt: sev-guest: Use AES GCM crypto library Nikunj A Dadhania
2023-10-11 18:56   ` Borislav Petkov
2023-10-12  4:40     ` Nikunj A. Dadhania
2023-10-12  7:45       ` Borislav Petkov
2023-10-12  8:27         ` Nikunj A. Dadhania
2023-08-14  5:52 ` [PATCH v4 02/14] virt: sev-guest: Move mutex to SNP guest device structure Nikunj A Dadhania
2023-08-14  5:52 ` [PATCH v4 03/14] virt: sev-guest: Replace dev_dbg with pr_debug Nikunj A Dadhania
2023-08-14  5:52 ` [PATCH v4 04/14] virt: sev-guest: Add SNP guest request structure Nikunj A Dadhania
2023-08-14  5:52 ` [PATCH v4 05/14] virt: sev-guest: Add vmpck_id to snp_guest_dev struct Nikunj A Dadhania
2023-08-14  5:52 ` [PATCH v4 06/14] x86/sev: Cache the secrets page address Nikunj A Dadhania
2023-08-14  5:52 ` [PATCH v4 07/14] x86/sev: Move and reorganize sev guest request api Nikunj A Dadhania
2023-08-14  5:52 ` [PATCH v4 08/14] x86/mm: Add generic guest initialization hook Nikunj A Dadhania
2023-08-14  5:52 ` [PATCH v4 09/14] x86/sev: Add Secure TSC support for SNP guests Nikunj A Dadhania
2023-08-14  5:52 ` [PATCH v4 10/14] x86/sev: Change TSC MSR behavior for Secure TSC enabled guests Nikunj A Dadhania
2023-08-14  5:52 ` [PATCH v4 11/14] x86/sev: Prevent RDTSC/RDTSCP interception " Nikunj A Dadhania
2023-08-14  5:52 ` [PATCH v4 12/14] x86/kvmclock: Skip kvmclock when Secure TSC is available Nikunj A Dadhania
2023-08-14  5:52 ` [PATCH v4 13/14] x86/tsc: Mark Secure TSC as reliable clocksource Nikunj A Dadhania
2023-08-14  5:52 ` [PATCH v4 14/14] x86/sev: Enable Secure TSC for SNP guests Nikunj A Dadhania
2023-08-28  3:47 ` [PATCH v4 00/14] Add Secure TSC support " Nikunj A. Dadhania
2023-10-04  5:35   ` Nikunj A. Dadhania
2023-10-04  7:01     ` Borislav Petkov
2023-10-05 13:57       ` Nikunj A. Dadhania [this message]
2023-10-05 14:32         ` 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=1f740bdd-666b-4686-8d04-1c28da9917bd@amd.com \
    --to=nikunj@amd.com \
    --cc=bp@alien8.de \
    --cc=dionnaglaze@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=pgonda@google.com \
    --cc=seanjc@google.com \
    --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