[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <046992ea-c201-016d-ee59-e1af72d8a6d8@amd.com>
Date: Tue, 14 Feb 2023 08:27:47 -0600
From: Tom Lendacky <thomas.lendacky@....com>
To: Dionna Amalie Glaze <dionnaglaze@...gle.com>
Cc: linux-kernel@...r.kernel.org, x86@...nel.org,
Paolo Bonzini <pbonzini@...hat.com>,
Joerg Roedel <jroedel@...e.de>,
Peter Gonda <pgonda@...gle.com>,
Thomas Gleixner <tglx@...utronix.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Ingo Molnar <mingo@...hat.com>,
Borislav Petkov <Borislav.Petkov@....com>,
"H. Peter Anvin" <hpa@...or.com>,
Venu Busireddy <venu.busireddy@...cle.com>,
Michael Roth <michael.roth@....com>,
"Kirill A. Shutemov" <kirill@...temov.name>,
Michael Sterritt <sterritt@...gle.com>
Subject: Re: [PATCH v14 1/3] virt/coco/sev-guest: Add throttling awareness
On 2/13/23 16:28, Dionna Amalie Glaze wrote:
>>
>> This should really be a new, separate patch.
>>
>
> I had it as a separate patch and squashed since I felt it necessary to
> be considered still a "Fixes" patch. Should both claim to fix the same
> patch?
If they both fix a bug, yes. You can have multiple patches that fix
different bugs that were all introduced by one commit.
Thanks,
Tom
>
>>
>> It looks like you will ensure throttling by continually calling the
>> hypervisor for 60 seconds, shouldn't there be a delay here?
>>
>
> I can change cond_resched() to sleep_timeout_killable(some_constant)
>
>>> - rc = snp_issue_guest_request(exit_code, &snp_dev->input, &err);
>>> + cond_resched();
>>> + goto retry;
>>>
>>> + }
>>
>> Nit, add a blank line here.
>>
>
> Will do.
>
>> Thanks,
>> Tom
>>
>
>
Powered by blists - more mailing lists