All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
To: Jerone Young <jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [kvm-ppc-devel] [PATCH] Add print for PowerPC qemu for failed
Date: Wed, 06 Feb 2008 11:25:38 +0000	[thread overview]
Message-ID: <47A99932.3050009@linux.vnet.ibm.com> (raw)
In-Reply-To: <4bbbf98ebf05ef77dbb6.1202249218-Zv899e0YUSbPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>

hi Jerone,
I think this is good for debugging to find unsupported hardware, but it should not be enabled by default (you could get a printf storm if a guest workload does stupid things). Maybe qemu has some debug/verbose options you can use.
And additionally it would be useful for the dcr_write patch to print the value it tried to write.
I also don't know if we really need that caps-locked in the output.

Jerone Young wrote:
> # HG changeset patch
> # User Jerone Young <jyoung5@us.ibm.com>
> # Date 1202249136 21600
> # Node ID 4bbbf98ebf05ef77dbb68e2131b3bc0764767c99
> # Parent  f8cab6a29bf3f34f1cbf4d1e6d7bd21809fd4184
> Add print for PowerPC qemu for failed DCR read/writes
> 
> This patch adds a print to notify of failed reads and rights. Currently
> we will still ignore them (until development is fully done). But this makes
> them easier to spot.
> 
> Signed-off-by: Jerone Young <jyoung5@us.ibm.com>
> 
> diff --git a/qemu/qemu-kvm-powerpc.c b/qemu/qemu-kvm-powerpc.c
> --- a/qemu/qemu-kvm-powerpc.c
> +++ b/qemu/qemu-kvm-powerpc.c
> @@ -178,13 +178,17 @@ int handle_powerpc_dcr_read(int vcpu, ui
>  int handle_powerpc_dcr_read(int vcpu, uint32_t dcrn, uint32_t *data)
>  {
>      CPUState *env = cpu_single_env;
> -    ppc_dcr_read(env->dcr_env, dcrn, data);
> +    if (ppc_dcr_read(env->dcr_env, dcrn, data) < 0)
> +        printf("DCR FAILED on READ at 0x%x\n", dcrn);
> + 
>      return 0; /* XXX ignore failed DCR ops */
>  }
> 
>  int handle_powerpc_dcr_write(int vcpu, uint32_t dcrn, uint32_t data)
>  {
>      CPUState *env = cpu_single_env;
> -    ppc_dcr_write(env->dcr_env, dcrn, data);
> +    if (ppc_dcr_write(env->dcr_env, dcrn, data) < 0)
> +        printf("DCR FAILED on WRITE at 0x%x\n", dcrn);
just a suggestion

        printf("%s - failed writing 0x%x @ 0x%x\n", dcrn, data);

> +
>      return 0; /* XXX ignore failed DCR ops */
>  }
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> kvm-ppc-devel mailing list
> kvm-ppc-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel


-- 

Grüsse / regards, 
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel

WARNING: multiple messages have this Message-ID (diff)
From: Christian Ehrhardt <ehrhardt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Jerone Young <jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [kvm-ppc-devel] [PATCH] Add print for PowerPC qemu for failed DCR read/writes
Date: Wed, 06 Feb 2008 12:25:38 +0100	[thread overview]
Message-ID: <47A99932.3050009@linux.vnet.ibm.com> (raw)
In-Reply-To: <4bbbf98ebf05ef77dbb6.1202249218-Zv899e0YUSbPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>

hi Jerone,
I think this is good for debugging to find unsupported hardware, but it should not be enabled by default (you could get a printf storm if a guest workload does stupid things). Maybe qemu has some debug/verbose options you can use.
And additionally it would be useful for the dcr_write patch to print the value it tried to write.
I also don't know if we really need that caps-locked in the output.

Jerone Young wrote:
> # HG changeset patch
> # User Jerone Young <jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> # Date 1202249136 21600
> # Node ID 4bbbf98ebf05ef77dbb68e2131b3bc0764767c99
> # Parent  f8cab6a29bf3f34f1cbf4d1e6d7bd21809fd4184
> Add print for PowerPC qemu for failed DCR read/writes
> 
> This patch adds a print to notify of failed reads and rights. Currently
> we will still ignore them (until development is fully done). But this makes
> them easier to spot.
> 
> Signed-off-by: Jerone Young <jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> 
> diff --git a/qemu/qemu-kvm-powerpc.c b/qemu/qemu-kvm-powerpc.c
> --- a/qemu/qemu-kvm-powerpc.c
> +++ b/qemu/qemu-kvm-powerpc.c
> @@ -178,13 +178,17 @@ int handle_powerpc_dcr_read(int vcpu, ui
>  int handle_powerpc_dcr_read(int vcpu, uint32_t dcrn, uint32_t *data)
>  {
>      CPUState *env = cpu_single_env;
> -    ppc_dcr_read(env->dcr_env, dcrn, data);
> +    if (ppc_dcr_read(env->dcr_env, dcrn, data) < 0)
> +        printf("DCR FAILED on READ at 0x%x\n", dcrn);
> + 
>      return 0; /* XXX ignore failed DCR ops */
>  }
> 
>  int handle_powerpc_dcr_write(int vcpu, uint32_t dcrn, uint32_t data)
>  {
>      CPUState *env = cpu_single_env;
> -    ppc_dcr_write(env->dcr_env, dcrn, data);
> +    if (ppc_dcr_write(env->dcr_env, dcrn, data) < 0)
> +        printf("DCR FAILED on WRITE at 0x%x\n", dcrn);
just a suggestion

        printf("%s - failed writing 0x%x @ 0x%x\n", dcrn, data);

> +
>      return 0; /* XXX ignore failed DCR ops */
>  }
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> kvm-ppc-devel mailing list
> kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel


-- 

Grüsse / regards, 
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2008-02-06 11:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 22:06 [kvm-ppc-devel] [PATCH] Add print for PowerPC qemu for failed DCR Jerone Young
2008-02-05 22:06 ` [PATCH] Add print for PowerPC qemu for failed DCR read/writes Jerone Young
     [not found] ` <4bbbf98ebf05ef77dbb6.1202249218-Zv899e0YUSbPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2008-02-06 11:25   ` Christian Ehrhardt [this message]
2008-02-06 11:25     ` [kvm-ppc-devel] " Christian Ehrhardt
     [not found]     ` <47A99932.3050009-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-02-06 17:06       ` [kvm-ppc-devel] [PATCH] Add print for PowerPC qemu for Hollis Blanchard
2008-02-06 17:06         ` [kvm-ppc-devel] [PATCH] Add print for PowerPC qemu for failed DCR read/writes Hollis Blanchard

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=47A99932.3050009@linux.vnet.ibm.com \
    --to=ehrhardt@linux.vnet.ibm.com \
    --cc=jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.