Kernel KVM-PPC virtualization development
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 03/23] Add PPC64 fields to vcpu structs
Date: Tue, 07 Jul 2009 15:42:31 +0000	[thread overview]
Message-ID: <4A536CE7.5070904@redhat.com> (raw)
In-Reply-To: <1246976262-4826-4-git-send-email-agraf@suse.de>

On 07/07/2009 05:17 PM, Alexander Graf wrote:
> We need to store more information than we currently have for vcpus
> when running on PPC64.
>
> So let's extend the internal struct definitions.
>
> Signed-off-by: Alexander Graf<agraf@suse.de>
> ---
>   arch/powerpc/include/asm/kvm_host.h |   80 ++++++++++++++++++++++++++++++++++-
>   1 files changed, 79 insertions(+), 1 deletions(-)
>
> diff --git a/arch/powerpc/include/asm/kvm_host.h b/arch/powerpc/include/asm/kvm_host.h
> index c9c930e..80eeef7 100644
> --- a/arch/powerpc/include/asm/kvm_host.h
> +++ b/arch/powerpc/include/asm/kvm_host.h
> @@ -37,6 +37,8 @@
>   #define KVM_NR_PAGE_SIZES	1
>   #define KVM_PAGES_PER_HPAGE(x)	(1UL<<31)
>
> +#define HPTEG_CACHE_NUM 1024
> +
>   struct kvm;
>   struct kvm_run;
>   struct kvm_vcpu;
> @@ -63,6 +65,17 @@ struct kvm_vcpu_stat {
>   	u32 dec_exits;
>   	u32 ext_intr_exits;
>   	u32 halt_wakeup;
> +#ifdef CONFIG_PPC64
> +	u32 pf_storage;
> +	u32 pf_instruc;
> +	u32 sp_storage;
> +	u32 sp_instruc;
> +	u32 queue_intr;
> +	u32 ld;
> +	u32 ld_slow;
> +	u32 st;
> +	u32 st_slow;
> +#endif
>   };
>
>    

My plan is to drop kvm_vcpu_stat in favor of tracepoints (you can have 
ftrace count tracepoints instead of recording them).

You can do that later if you want to avoid the churn.

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


      reply	other threads:[~2009-07-07 15:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07 14:17 [PATCH 03/23] Add PPC64 fields to vcpu structs Alexander Graf
2009-07-07 15:42 ` Avi Kivity [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=4A536CE7.5070904@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm-ppc@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