qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel Southern <gabriel.southern@gmail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] SPARC kernel oops with logging
Date: Wed, 6 May 2009 14:01:29 -0700	[thread overview]
Message-ID: <3c2bf46d0905061401u19dc1fa9tf5a15a0b65ab81aa@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580905061157u580ce687t7cf6e9dbd2c9d0ac@mail.gmail.com>

Thanks, this patch does seem to have fixed the problem for me.

-Gabriel

>
> I think this patch should fix the problem.
>
> Sparc disassembler wants to check previous addresses for some stuff
> and this may actually cause faults if the address is close to page
> start, because of the function used for the memory access.
>
> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
> ---
>  disas.c |    5 +----
>  1 files changed, 1 insertions(+), 4 deletions(-)
>
> diff --git a/disas.c b/disas.c
> index 37f7433..6ed31e3 100644
> --- a/disas.c
> +++ b/disas.c
> @@ -33,10 +33,7 @@ target_read_memory (bfd_vma memaddr,
>                     int length,
>                     struct disassemble_info *info)
>  {
> -    int i;
> -    for(i = 0; i < length; i++) {
> -        myaddr[i] = ldub_code(memaddr + i);
> -    }
> +    cpu_memory_rw_debug(cpu_single_env, memaddr, myaddr, length, 0);
>     return 0;
>  }
>
> --
> 1.6.2.4
>

  reply	other threads:[~2009-05-06 21:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 21:56 [Qemu-devel] SPARC kernel oops with logging Gabriel Southern
2009-05-05 15:29 ` Blue Swirl
2009-05-05 23:37   ` Gabriel Southern
2009-05-06 18:57     ` Blue Swirl
2009-05-06 21:01       ` Gabriel Southern [this message]
2009-05-07 17:15         ` Blue Swirl

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=3c2bf46d0905061401u19dc1fa9tf5a15a0b65ab81aa@mail.gmail.com \
    --to=gabriel.southern@gmail.com \
    --cc=blauwirbel@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).