All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Liu Yu-B13201 <Yu.Liu@freescale.com>
Cc: kvm-ppc <kvm-ppc@vger.kernel.org>,
	Nathan Froyd <froydnj@codesourcery.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: [PATCH 2/5] Fix booke registers init
Date: Sat, 25 Jul 2009 10:04:31 +0000	[thread overview]
Message-ID: <4A6AD8AF.3080509@web.de> (raw)
In-Reply-To: <1248511217-22681-3-git-send-email-yu.liu@freescale.com>

[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]

Liu Yu wrote:
> Commit 8d2ba1fb9c8e7006e10d71fa51a020977f14c8b0
> introduces a new new reset order.
> 
> So that we have to synchronize registers explicitly.
> 
> Signed-off-by: Liu Yu <yu.liu-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
> ---
>  hw/ppc440_bamboo.c     |    4 +++-
>  hw/ppce500_mpc8544ds.c |    4 +++-
>  2 files changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/hw/ppc440_bamboo.c b/hw/ppc440_bamboo.c
> index d9ef3ec..f1ba130 100644
> --- a/hw/ppc440_bamboo.c
> +++ b/hw/ppc440_bamboo.c
> @@ -182,8 +182,10 @@ static void bamboo_init(ram_addr_t ram_size,
>          /* XXX we currently depend on KVM to create some initial TLB entries. */
>      }
>  
> -    if (kvm_enabled())
> +    if (kvm_enabled()) {
> +        kvm_arch_put_registers(env);
>          kvmppc_init();
> +    }
>  }
>  
>  static QEMUMachine bamboo_machine = {
> diff --git a/hw/ppce500_mpc8544ds.c b/hw/ppce500_mpc8544ds.c
> index c0e367d..f1b3c1a 100644
> --- a/hw/ppce500_mpc8544ds.c
> +++ b/hw/ppce500_mpc8544ds.c
> @@ -276,8 +276,10 @@ static void mpc8544ds_init(ram_addr_t ram_size,
>          /* XXX we currently depend on KVM to create some initial TLB entries. */
>      }
>  
> -    if (kvm_enabled())
> +    if (kvm_enabled()) {
> +        kvm_arch_put_registers(env);
>          kvmppc_init();
> +    }
>  
>      return;
>  }

These are required when loading a device tree and, thus, changing some
registers after cpu_init, right? Then please add
cpu_synchronize_state(env, 1) to the corresponding code blocks instead
of this explicit, kvm-specific loading.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  parent reply	other threads:[~2009-07-25 10:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-25  8:40 [PATCH 0/5] Liu Yu
2009-07-25  8:40 ` [PATCH 1/5] Fix kvmppc build error Liu Yu
2009-07-25  8:40   ` [PATCH 2/5] Fix booke registers init Liu Yu
2009-07-25  8:40     ` [PATCH 3/5] Add guest debug support for kvmppc Liu Yu
2009-07-25  8:40       ` [PATCH 4/5] Add eaddr translator for fsl_booke mmu Liu Yu
2009-07-25  8:40         ` [PATCH 5/5] guest debug init for 440 and e500 core Liu Yu
2009-07-25 10:27           ` Jan Kiszka
2009-07-25 10:18       ` [PATCH 3/5] Add guest debug support for kvmppc Jan Kiszka
2009-07-28  2:01         ` Liu Yu-B13201
2009-07-25 10:04     ` Jan Kiszka [this message]
2009-07-27 10:31       ` [PATCH 2/5] Fix booke registers init Liu Yu-B13201
2009-07-25 10:43 ` [PATCH 0/5] Jan Kiszka
2009-07-27 10:39   ` Liu Yu-B13201
2009-07-27 13:14 ` Nathan Froyd
2009-07-28  8:11   ` Liu Yu-B13201
2009-07-28 12:40 ` Nathan Froyd

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=4A6AD8AF.3080509@web.de \
    --to=jan.kiszka@web.de \
    --cc=Yu.Liu@freescale.com \
    --cc=froydnj@codesourcery.com \
    --cc=hollisb@us.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=qemu-devel@nongnu.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.