[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yl7c06VX5Pf4ZKsa@google.com>
Date: Tue, 19 Apr 2022 16:01:23 +0000
From: Sean Christopherson <seanjc@...gle.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Paolo Bonzini <pbonzini@...hat.com>, KVM <kvm@...r.kernel.org>,
Peter Gonda <pgonda@...gle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the kvm tree
On Tue, Apr 19, 2022, Stephen Rothwell wrote:
> Hi all,
>
> After merging the kvm tree, today's linux-next build (arm64 defconfig)
> failed like this:
>
> arch/arm64/kvm/psci.c: In function 'kvm_prepare_system_event':
> arch/arm64/kvm/psci.c:184:32: error: 'struct <anonymous>' has no member named 'flags'
> 184 | vcpu->run->system_event.flags = flags;
> | ^
>
> Caused by commit
>
> c24a950ec7d6 ("KVM, SEV: Add KVM_EXIT_SHUTDOWN metadata for SEV-ES")
>
> In this commit, the uapi structure changes do not match the documentation
> changes :-( Does it matter that the ABI may be changed by this commit
> (depending on the alignment of the structure members)?
Yeah, it's a bit of mess. I believe we have a way out, waiting on Paolo to weigh in.
https://lore.kernel.org/all/YlisiF4BU6Uxe+iU@google.com
Powered by blists - more mailing lists