[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241127065510.GBZ0bCTl8hptbdph2p@fat_crate.local>
Date: Wed, 27 Nov 2024 07:55:10 +0100
From: Borislav Petkov <bp@...en8.de>
To: Xin Li <xin@...or.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, seanjc@...gle.com, pbonzini@...hat.com,
corbet@....net, tglx@...utronix.de, mingo@...hat.com,
dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
luto@...nel.org, peterz@...radead.org, andrew.cooper3@...rix.com
Subject: Re: [PATCH v3 09/27] KVM: VMX: Do not use
MAX_POSSIBLE_PASSTHROUGH_MSRS in array definition
On Tue, Nov 26, 2024 at 10:46:09PM -0800, Xin Li wrote:
> Right. It triggered me to look at the code further, though, I think the
> existing code could be written in a better way no matter whether I need
> to add more MSRs. And whoever wants to add more won't need to increase
> MAX_POSSIBLE_PASSTHROUGH_MSRS (ofc unless overflow 64).
But do you see what I mean?
This patch is "all over the place": what are you actually fixing?
And more importantly, why is it part of this series?
Questions over questions.
So can you pls concentrate and spell out for me what is going on here...
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists