qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] sparc32 add a few more ASI
Date: Mon, 10 Dec 2007 22:11:32 +0200	[thread overview]
Message-ID: <f43fc5580712101211y7ea29172led5387cc89f305b9@mail.gmail.com> (raw)
In-Reply-To: <475C5217.2060509@earthlink.net>

On 12/9/07, Robert Reif <reif@earthlink.net> wrote:
>
>
> diff -p -u -r1.60 op_helper.c
> --- target-sparc/op_helper.c    28 Nov 2007 18:08:28 -0000      1.60
> +++ target-sparc/op_helper.c    9 Dec 2007 20:33:02 -0000
> @@ -411,6 +411,9 @@ void helper_ld_asi(int asi, int size, in
>              break;
>          }
>          break;
> +    case 0x39: /* data cache diagnostic register */
> +        ret = 0;
> +        break;
>      case 0x21 ... 0x2d: /* MMU passthrough, unassigned */
>      default:
>          do_unassigned_access(T0, 0, 0, 1);
> @@ -703,9 +706,13 @@ void helper_st_asi(int asi, int size)
>              }
>          }
>          return;
> -    case 0x31: /* Ross RT620 I-cache flush */
> +    case 0x30: /* store buffer tags */
> +    case 0x31: /* store buffer data or Ross RT620 I-cache flush */
> +    case 0x32: /* store buffer control */
>      case 0x36: /* I-cache flash clear */
>      case 0x37: /* D-cache flash clear */
> +    case 0x38: /* breakpoint diagnostics */
> +    case 0x4c: /* breakpoint action */
>          break;
>      case 9: /* Supervisor code access, XXX */
>      case 0x21 ... 0x2d: /* MMU passthrough, unassigned */

Thanks, applied.

Hardware breakpoint support could be useful, though GDB works without it.

      reply	other threads:[~2007-12-10 20:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-09 20:37 [Qemu-devel] [PATCH] sparc32 add a few more ASI Robert Reif
2007-12-10 20:11 ` Blue Swirl [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=f43fc5580712101211y7ea29172led5387cc89f305b9@mail.gmail.com \
    --to=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).