[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHVum0dHKAxqm3zk7zCdmY=BTFZYyOS-nGqH4WbYcuoVXDqjWw@mail.gmail.com>
Date: Mon, 6 Mar 2023 10:41:50 -0800
From: Vipin Sharma <vipinsh@...gle.com>
To: seanjc@...gle.com, pbonzini@...hat.com, maz@...nel.org,
james.morse@....com, suzuki.poulose@....com,
oliver.upton@...ux.dev, yuzenghui@...wei.com,
borntraeger@...ux.ibm.com, frankja@...ux.ibm.com,
imbrenda@...ux.ibm.com, david@...hat.com
Cc: dmatlack@...gle.com, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [Patch v2 0/4] Common KVM exit reason test assertions and exit
reason sync
On Fri, Feb 3, 2023 at 5:45 PM Vipin Sharma <vipinsh@...gle.com> wrote:
>
> Hi,
>
> This patch seris is extracted from
> https://lore.kernel.org/lkml/20221212183720.4062037-1-vipinsh@google.com/
> series.
>
> Specifically, patch 12 is taken out from there and now expanded in to
> this series.
>
> This patch series contains following changes:
>
> Patch 1 & 2:
> Make a macro to clean up all KVM exit reason test assertion.
>
> There are few places where explicit run->exit_reason are used but they
> cannot be replaced with current macro.
>
> I used following command KVM selftests directory and changed each
> occurrence:
> grep "run->exit_reason" -nir ./
>
> Patch 3:
> This is from Sean Christopherson. Adding a macro to generate KVM
> exit strings.
>
> Patch 4:
> Sync KVM_EXIT_* reasons to sefltests. Many reasons are not present in
> selftest code.
>
> v2:
> - Improve test assert message.
> - Add macro to generate KVM_EXIT_* reason strings.
> - Update selftests KVM_EXIT_ reasons to latest version.
>
> v1: https://lore.kernel.org/lkml/20221212183720.4062037-13-vipinsh@google.com/
Any update/feedback on this series?
Powered by blists - more mailing lists