[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <85430f7e-93e0-3652-0705-9cf6e948a9d8@redhat.com>
Date: Wed, 25 Mar 2020 17:08:03 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Randy Dunlap <rdunlap@...radead.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
KVM <kvm@...r.kernel.org>,
Sean Christopherson <sean.j.christopherson@...el.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
Joerg Roedel <joro@...tes.org>
Subject: Re: linux-next: Tree for Mar 25 (arch/x86/kvm/)
On 25/03/20 16:57, Randy Dunlap wrote:
>> Randy, can you test it with your compiler?
> Nope, no help. That's the wrong location.
> Need a patch for this:
>>> 24 (only showing one of them here) BUILD_BUG() errors in arch/x86/kvm/cpuid.h
>>> function __cpuid_entry_get_reg(), for the default: case.
Doh, right. I think the only solution for that one is to degrade it to
WARN_ON(1).
Paolo
Powered by blists - more mailing lists