[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240423132252.GJZie2LGgVszU_XejZ@fat_crate.local>
Date: Tue, 23 Apr 2024 15:22:52 +0200
From: Borislav Petkov <bp@...en8.de>
To: "Nikunj A. Dadhania" <nikunj@....com>
Cc: linux-kernel@...r.kernel.org, thomas.lendacky@....com, x86@...nel.org,
kvm@...r.kernel.org, mingo@...hat.com, tglx@...utronix.de,
dave.hansen@...ux.intel.com, pgonda@...gle.com, seanjc@...gle.com,
pbonzini@...hat.com
Subject: Re: [PATCH v8 07/16] x86/sev: Move and reorganize sev guest request
api
On Tue, Apr 23, 2024 at 09:56:38AM +0530, Nikunj A. Dadhania wrote:
> Yes, I had tried that compilation/guest boot does not break at this
> stage. That was the reason for intermixing movement and code change.
>
> Let me give a second stab at this and I will try just to make sure
> compilation does not break.
Yes, you can also do preparatory changes which get removed later, if
that helps.
It is perfectly fine to have a couple more patches preparing and doing
the move which are trivial to review and verify vs one combo patch which
makes you stare at it a long time and you're still not sure it doesn't
change something...
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists