[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <43a47609b43641bd74f96d86783f984295e3d87d.camel@redhat.com>
Date: Thu, 28 Sep 2023 13:41:30 +0300
From: Maxim Levitsky <mlevitsk@...hat.com>
To: Paolo Bonzini <pbonzini@...hat.com>, kvm@...r.kernel.org
Cc: Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
Sean Christopherson <seanjc@...gle.com>,
Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH v2 2/4] KVM: x86: add more information to the kvm_entry
tracepoint
У вт, 2023-09-26 у 18:39 +0200, Paolo Bonzini пише:
> On 9/24/23 14:44, Maxim Levitsky wrote:
> > + __field( u32, inj_info )
> > + __field( u32, inj_info_err )
> > + __field( bool, guest_mode )
> > + __field( bool, req_imm_exit )
> > + ),
>
> As anticipated in patch 1 I'm not so sure about adding req_imm_exit here
> but also (especially) in kvm_exit. I do believe it should be traced,
> I'm not sure it's needed in kvm_entry+kvm_exit as opposed to just a
> separate tracepoint.
I will drop guest_mode.
Best regards,
Maxim Levitsky
>
> Paolo
>
Powered by blists - more mailing lists