[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160413105331.GA30907@gmail.com>
Date: Wed, 13 Apr 2016 12:53:31 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Alexander Shishkin <alexander.shishkin@...ux.intel.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Gleb Natapov <gleb@...nel.org>,
Paolo Bonzini <pbonzini@...hat.com>, x86@...nel.org,
kvm@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
linux-kernel@...r.kernel.org, tglx@...utronix.de, hpa@...or.com,
Arnaldo Carvalho de Melo <acme@...radead.org>,
Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH] perf/x86/intel/pt: Don't die on VMXON
* Alexander Shishkin <alexander.shishkin@...ux.intel.com> wrote:
> Ingo Molnar <mingo@...nel.org> writes:
>
> >> @@ -3144,6 +3146,8 @@ static void vmclear_local_loaded_vmcss(void)
> >> static void kvm_cpu_vmxoff(void)
> >> {
> >> asm volatile (__ex(ASM_VMX_VMXOFF) : : : "cc");
> >> +
> >> + intel_pt_vmx(0);
> >> }
> >
> > Yeah so the name intel_pt_vmx() is pretty information-free because it has no verb,
> > only nouns - please name new functions descriptively to after what they do!
>
> I do agree that it can use a better name (and this is a second attempt
> already).
>
> > Something like intel_pt_set_vmx_state() or so?
>
> Hmm how about intel_pt_handle_vmx()? Ideally, akin to the VMXON/VMXOFF insns,
> this could be two functions (intel_pt_handle_vmx{on,off}()) if the global
> namespace can take it.
Sure, intel_pt_handle_vmx(0/1) sounds good too. I wouldn't split it into two
functions ...
Thanks,
Ingo
Powered by blists - more mailing lists