From: Maxim Levitsky <mlevitsk@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Cc: Kieran Bingham <kbingham@kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Andrew Jones <drjones@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, Johannes Berg <johannes.berg@intel.com>,
Wanpeng Li <wanpengli@tencent.com>,
"H. Peter Anvin" <hpa@zytor.com>, Jessica Yu <jeyu@kernel.org>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Yang Weijiang <weijiang.yang@intel.com>,
linux-kernel@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Shuah Khan <shuah@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v3 0/6] KVM: my debug patch queue
Date: Wed, 11 Aug 2021 16:22:23 +0300 [thread overview]
Message-ID: <bb7568d08ea7d3598d71db7631d56b9f288d3f32.camel@redhat.com> (raw)
In-Reply-To: <1646763f-9f92-bb67-f358-9b17c8000b12@redhat.com>
On Wed, 2021-08-11 at 15:10 +0200, Paolo Bonzini wrote:
> On 11/08/21 14:29, Maxim Levitsky wrote:
> > Hi!
> >
> > I would like to publish two debug features which were needed for other stuff
> > I work on.
> >
> > One is the reworked lx-symbols script which now actually works on at least
> > gdb 9.1 (gdb 9.2 was reported to fail to load the debug symbols from the kernel
> > for some reason, not related to this patch) and upstream qemu.
> >
> > The other feature is the ability to trap all guest exceptions (on SVM for now)
> > and see them in kvmtrace prior to potential merge to double/triple fault.
> >
> > This can be very useful and I already had to manually patch KVM a few
> > times for this.
> > I will, once time permits, implement this feature on Intel as well.
> >
> > V2:
> >
> > * Some more refactoring and workarounds for lx-symbols script
> >
> > * added KVM_GUESTDBG_BLOCKIRQ flag to enable 'block interrupts on
> > single step' together with KVM_CAP_SET_GUEST_DEBUG2 capability
> > to indicate which guest debug flags are supported.
> >
> > This is a replacement for unconditional block of interrupts on single
> > step that was done in previous version of this patch set.
> > Patches to qemu to use that feature will be sent soon.
> >
> > * Reworked the the 'intercept all exceptions for debug' feature according
> > to the review feedback:
> >
> > - renamed the parameter that enables the feature and
> > moved it to common kvm module.
> > (only SVM part is currently implemented though)
> >
> > - disable the feature for SEV guests as was suggested during the review
> > - made the vmexit table const again, as was suggested in the review as well.
> >
> > V3:
> > * Modified a selftest to cover the KVM_GUESTDBG_BLOCKIRQ
> > * Rebased on kvm/queue
> >
> > Best regards,
> > Maxim Levitsky
> >
> > Maxim Levitsky (6):
> > KVM: SVM: split svm_handle_invalid_exit
> > KVM: x86: add force_intercept_exceptions_mask
> > KVM: SVM: implement force_intercept_exceptions_mask
> > scripts/gdb: rework lx-symbols gdb script
> > KVM: x86: implement KVM_GUESTDBG_BLOCKIRQ
> > KVM: selftests: test KVM_GUESTDBG_BLOCKIRQ
> >
> > Documentation/virt/kvm/api.rst | 1 +
> > arch/x86/include/asm/kvm_host.h | 5 +-
> > arch/x86/include/uapi/asm/kvm.h | 1 +
> > arch/x86/kvm/svm/svm.c | 87 +++++++-
> > arch/x86/kvm/svm/svm.h | 6 +-
> > arch/x86/kvm/x86.c | 12 +-
> > arch/x86/kvm/x86.h | 2 +
> > kernel/module.c | 8 +-
> > scripts/gdb/linux/symbols.py | 203 ++++++++++++------
> > .../testing/selftests/kvm/x86_64/debug_regs.c | 24 ++-
> > 10 files changed, 266 insertions(+), 83 deletions(-)
> >
>
> Queued 1-5-6.
>
> For patches 2 and 3, please add VMX support too.
>
> For patch 4, it's not KVM :) so please submit it separately.
Thanks!
I will do this!
Best regards,
Maxim Levitsky
>
> Paolo
>
prev parent reply other threads:[~2021-08-11 13:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 12:29 [PATCH v3 0/6] KVM: my debug patch queue Maxim Levitsky
2021-08-11 12:29 ` [PATCH v3 1/6] KVM: SVM: split svm_handle_invalid_exit Maxim Levitsky
2021-08-11 12:29 ` [PATCH v3 2/6] KVM: x86: add force_intercept_exceptions_mask Maxim Levitsky
2021-09-02 16:56 ` Sean Christopherson
2022-02-08 14:34 ` Maxim Levitsky
2022-03-08 23:37 ` Sean Christopherson
2022-03-09 12:31 ` Maxim Levitsky
2022-03-09 14:03 ` Paolo Bonzini
2022-03-09 15:40 ` Sean Christopherson
2021-08-11 12:29 ` [PATCH v3 3/6] KVM: SVM: implement force_intercept_exceptions_mask Maxim Levitsky
2021-08-11 14:26 ` Maxim Levitsky
2021-09-02 17:34 ` Sean Christopherson
2022-02-08 14:35 ` Maxim Levitsky
2021-08-11 12:29 ` [PATCH v3 4/6] scripts/gdb: rework lx-symbols gdb script Maxim Levitsky
2021-08-11 12:29 ` [PATCH v3 5/6] KVM: x86: implement KVM_GUESTDBG_BLOCKIRQ Maxim Levitsky
2021-08-11 12:29 ` [PATCH v3 6/6] KVM: selftests: test KVM_GUESTDBG_BLOCKIRQ Maxim Levitsky
2021-09-06 11:20 ` Paolo Bonzini
2021-09-06 21:03 ` Maxim Levitsky
2021-11-01 15:43 ` Vitaly Kuznetsov
2021-11-01 16:19 ` Maxim Levitsky
2021-11-01 23:21 ` Sean Christopherson
2021-11-02 10:46 ` Vitaly Kuznetsov
2021-11-02 15:53 ` Sean Christopherson
2021-11-02 16:18 ` Vitaly Kuznetsov
2021-11-02 18:45 ` Sean Christopherson
2021-11-03 9:04 ` Maxim Levitsky
2021-08-11 13:10 ` [PATCH v3 0/6] KVM: my debug patch queue Paolo Bonzini
2021-08-11 13:22 ` Maxim Levitsky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bb7568d08ea7d3598d71db7631d56b9f288d3f32.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=drjones@redhat.com \
--cc=hpa@zytor.com \
--cc=jan.kiszka@siemens.com \
--cc=jeyu@kernel.org \
--cc=jmattson@google.com \
--cc=johannes.berg@intel.com \
--cc=joro@8bytes.org \
--cc=kbingham@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=weijiang.yang@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox