[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YCRMY17WEdpJYd3C@google.com>
Date: Wed, 10 Feb 2021 13:13:07 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: "Woodhouse, David" <dwmw@...zon.co.uk>
Cc: "pbonzini@...hat.com" <pbonzini@...hat.com>,
"jmattson@...gle.com" <jmattson@...gle.com>,
"joro@...tes.org" <joro@...tes.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"vkuznets@...hat.com" <vkuznets@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"wanpengli@...cent.com" <wanpengli@...cent.com>
Subject: Re: [PATCH 5/5] KVM: x86/xen: Explicitly pad struct compat_vcpu_info
to 64 bytes
On Wed, Feb 10, 2021, Woodhouse, David wrote:
> On Wed, 2021-02-10 at 10:26 -0800, Sean Christopherson wrote:
> So it isn't clear the additionally padding really buys us anything; if
> we play this game without knowing the ABI we'd be screwed anyway. But
> it doesn't hurt.
Ya, this is purely for folks reading the code and wondering how 62==64.
Powered by blists - more mailing lists