[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6d92f593-77d8-4008-af3f-5b5bc790b87b@intel.com>
Date: Thu, 7 Mar 2024 11:25:49 +1300
From: "Huang, Kai" <kai.huang@...el.com>
To: Isaku Yamahata <isaku.yamahata@...ux.intel.com>
CC: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
<isaku.yamahata@...el.com>, <kvm@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <isaku.yamahata@...il.com>, Paolo Bonzini
<pbonzini@...hat.com>, <erdemaktas@...gle.com>, Sean Christopherson
<seanjc@...gle.com>, Sagi Shahar <sagis@...gle.com>, <chen.bo@...el.com>,
<hang.yuan@...el.com>, <tina.zhang@...el.com>
Subject: Re: [PATCH v19 008/130] x86/tdx: Warning with 32bit build
shift-count-overflow
>> Please just clarify (at least):
>>
>> - Does this problem exist in upstream code?
>
> No.
>
>> - If it does, what is the root cause, and how to reproduce?
>
> v18 had a problem because it has stub function. v19 doesn't have problem because
> it deleted the stub function.
What is the "stub function"??
If "v19 doesn't have problem", why do you even _need_ this patch??
I am tired of guessing, but I don't care anymore given it's not a
problem in upstream code.
Powered by blists - more mailing lists