public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Jerone Young <jyoung5@us.ibm.com>
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 2 of 3] Move KVM TRACE DEFINITIONS to common header
Date: Sun, 29 Jun 2008 14:50:34 +0300	[thread overview]
Message-ID: <4867770A.1080707@qumranet.com> (raw)
In-Reply-To: <463b4c3970c638fc3537.1213935554@thinkpadL>

Jerone Young wrote:
> 3 files changed, 40 insertions(+), 40 deletions(-)
> include/asm-x86/kvm.h      |   22 ----------------------
> include/asm-x86/kvm_host.h |   18 ------------------
> include/linux/kvm_host.h   |   40 ++++++++++++++++++++++++++++++++++++++++
>
>
> This patch moves moves definitions required to use kvm trace from x86 specific kvm headers to common kvm headers.
>
>   

I applied patch 1, but:

> 						vcpu, 0, 0, 0, 0, 0, 0)
>  
>  #ifdef CONFIG_64BIT
>  #define KVM_EX_ENTRY ".quad"
> diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
> --- a/include/linux/kvm_host.h
> +++ b/include/linux/kvm_host.h
> @@ -322,6 +322,46 @@ extern struct dentry *kvm_debugfs_dir;
>  #ifdef CONFIG_KVM_TRACE
>  int kvm_trace_ioctl(unsigned int ioctl, unsigned long arg);
>  void kvm_trace_cleanup(void);
> +#define KVM_TRC_INJ_VIRQ         (KVM_TRC_HANDLER + 0x02)
> +#define KVM_TRC_REDELIVER_EVT    (KVM_TRC_HANDLER + 0x03)
> +#define KVM_TRC_PEND_INTR        (KVM_TRC_HANDLER + 0x04)
> +#define KVM_TRC_IO_READ          (KVM_TRC_HANDLER + 0x05)
> +#define KVM_TRC_IO_WRITE         (KVM_TRC_HANDLER + 0x06)
> +#define KVM_TRC_CR_READ          (KVM_TRC_HANDLER + 0x07)
> +#define KVM_TRC_CR_WRITE         (KVM_TRC_HANDLER + 0x08)
> +#define KVM_TRC_DR_READ          (KVM_TRC_HANDLER + 0x09)
> +#define KVM_TRC_DR_WRITE         (KVM_TRC_HANDLER + 0x0A)
> +#define KVM_TRC_MSR_READ         (KVM_TRC_HANDLER + 0x0B)
> +#define KVM_TRC_MSR_WRITE        (KVM_TRC_HANDLER + 0x0C)
> +#define KVM_TRC_CPUID            (KVM_TRC_HANDLER + 0x0D)
> +#define KVM_TRC_INTR             (KVM_TRC_HANDLER + 0x0E)
> +#define KVM_TRC_NMI              (KVM_TRC_HANDLER + 0x0F)
> +#define KVM_TRC_VMMCALL          (KVM_TRC_HANDLER + 0x10)
> +#define KVM_TRC_HLT              (KVM_TRC_HANDLER + 0x11)
> +#define KVM_TRC_CLTS             (KVM_TRC_HANDLER + 0x12)
> +#define KVM_TRC_LMSW             (KVM_TRC_HANDLER + 0x13)
> +#define KVM_TRC_APIC_ACCESS      (KVM_TRC_HANDLER + 0x14)
> +#define KVM_TRC_TDP_FAULT        (KVM_TRC_HANDLER + 0x15)
>  #else
>  static inline
>  int kvm_trace_ioctl(unsigned int ioctl, unsigned long arg)
>   

This hides the defines from the public interface.  The KVM_TRC_* 
constants should be in kvm.h.


-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2008-06-29 11:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20  4:19 [PATCH 0 of 3] Add ability for KVM TRACE to work on other archs Jerone Young
2008-06-20  4:19 ` [PATCH 1 of 3] Remove use of bit fields in kvm trace structure Jerone Young
2008-06-20 16:59   ` Hollis Blanchard
2008-06-23  2:33   ` Avi Kivity
2008-06-20  4:19 ` [PATCH 2 of 3] Move KVM TRACE DEFINITIONS to common header Jerone Young
2008-06-29 11:50   ` Avi Kivity [this message]
2008-07-01 19:59     ` Hollis Blanchard
2008-07-01 21:23       ` [PATCH 2 of 3] [v2] " Hollis Blanchard
2008-07-05  9:35         ` Avi Kivity
2008-06-20  4:19 ` [PATCH 3 of 3] Add new KVM TRACE events Jerone Young

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=4867770A.1080707@qumranet.com \
    --to=avi@qumranet.com \
    --cc=jyoung5@us.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.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