All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: akpm@linux-foundation.org, Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Avi Kivity <avi@qumranet.com>,
	kvm@vger.kernel.org, "Feng(Eric) Liu" <eric.e.liu@intel.com>
Subject: Re: [patch 4/4] KVM-trace port to tracepoints
Date: Thu, 17 Jul 2008 11:52:43 -0500	[thread overview]
Message-ID: <487F78DB.2070303@codemonkey.ws> (raw)
In-Reply-To: <20080717160003.359557938@polymtl.ca>

Hi Mathieu,

It's difficult to review your patches because they aren't inlined.

At any rate, this patches are unusable with SVM.  They try to execute VT 
instructions unconditionally.  For instance, you changed:
>
> -    KVMTRACE_1D(INTR, vcpu, vmcs_read32(VM_EXIT_INTR_INFO), handler);
> +    trace_kvm_intr(vcpu);

Which lived in VT-specific code (vmx.c)

To:

> +static void probe_kvm_intr(struct kvm_vcpu *vcpu)
> +{
> +    kvm_add_trace(KVM_TRC_INTR, vcpu, 1,
> +        (u32 []){ vmcs_read32(VM_EXIT_INTR_INFO) });
> +}
> +

Which lives in common code (kvm_trace.c).  But vmcs_read32() is 
VT-specific and should not be used in common code so this motion is 
wrong.  Why not just pass more arguments to probe_kvm_intr()?  Then your 
first two patches can be dropped completely.

Regards,

Anthony Liguori

Mathieu Desnoyers wrote:

  parent reply	other threads:[~2008-07-17 16:53 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 15:57 [patch 0/4] Port KVM-trace to tracepoints Mathieu Desnoyers
2008-07-17 15:57 ` [patch 1/4] kvm move VMCS Encodings to system headers Mathieu Desnoyers
2008-07-17 15:57 ` [patch 2/4] kvm move VMCS read " Mathieu Desnoyers
2008-07-17 15:57 ` [patch 3/4] KVM move register read-write " Mathieu Desnoyers
2008-07-17 15:57 ` [patch 4/4] KVM-trace port to tracepoints Mathieu Desnoyers
2008-07-17 16:49   ` Jan Kiszka
2008-07-17 17:28     ` Mathieu Desnoyers
2008-07-22 16:04       ` Jan Kiszka
2008-07-22 18:46         ` Avi Kivity
2008-07-23  7:49           ` Peter Zijlstra
2008-07-23  8:08             ` Avi Kivity
2008-07-23  8:55               ` Peter Zijlstra
2008-07-23  9:32                 ` Avi Kivity
2008-07-23  9:53                   ` Peter Zijlstra
2008-07-23 13:15                     ` Mathieu Desnoyers
2008-07-23 10:03                 ` Christoph Hellwig
2008-07-23 10:08                   ` Avi Kivity
2008-07-23 10:13                     ` Christoph Hellwig
2008-07-23 13:20               ` Mathieu Desnoyers
2008-07-17 16:52   ` Anthony Liguori [this message]
2008-07-17 17:04     ` Mathieu Desnoyers
2008-07-22 18:42 ` [patch 0/4] Port KVM-trace " Avi Kivity
2008-07-22 19:16   ` Frank Ch. Eigler
2008-07-22 19:31     ` Avi Kivity
2008-07-22 19:54       ` Frank Ch. Eigler
2008-07-22 22:12       ` [patch 0/4] Port KVM-trace to tracepoints -> LTTng ? Mathieu Desnoyers
2008-07-27 10:11         ` Avi Kivity
2008-07-28  0:54           ` [RFC] LTTng merge plan Mathieu Desnoyers
2008-07-28  0:54             ` Mathieu Desnoyers
2008-07-29 16:18             ` Frank Ch. Eigler
2008-07-29 16:18               ` Frank Ch. Eigler
2008-07-29 17:01               ` Mathieu Desnoyers
2008-07-29 17:01                 ` Mathieu Desnoyers
     [not found]                 ` <20080729211543.GB17097@redhat.com>
2008-07-29 22:41                   ` module-placed markers/tracepoints Mathieu Desnoyers
2008-07-29 23:01                     ` Frank Ch. Eigler
2008-07-29 23:19                       ` Mathieu Desnoyers
2008-07-30  1:40                     ` Rusty Russell
2008-07-30  2:27                       ` [PATCH] Module : call synchronize_sched() between module exit() and free Mathieu Desnoyers
2008-07-30  3:04                         ` Rusty Russell
2008-07-30  4:05                           ` Mathieu Desnoyers
2008-07-30 11:40                         ` Frank Ch. Eigler
2008-07-30 14:09                           ` Mathieu Desnoyers
2008-07-31  0:54                             ` Rusty Russell

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=487F78DB.2070303@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=akpm@linux-foundation.org \
    --cc=avi@qumranet.com \
    --cc=eric.e.liu@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.