qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Richard Henderson <rth@twiddle.net>, patches@linaro.org
Subject: Re: [Qemu-devel] [RFC] hw/alpha/typhoon: Stop calling cpu_unassigned_access()
Date: Mon, 10 Dec 2018 12:14:33 -0600	[thread overview]
Message-ID: <4271875c-faeb-ca7f-413c-df085b4a7da6@linaro.org> (raw)
In-Reply-To: <20181210173350.13073-1-peter.maydell@linaro.org>

On 12/10/18 11:33 AM, Peter Maydell wrote:
> The typhoon MemoryRegionOps callbacks directly call
> cpu_unassigned_access(), presumably as the old-fashioned way
> to provoke a CPU exception.  This won't work since commit
> 6ad4d7eed05a1e235 when we switched Alpha over to the
> transaction_failed hook API, because now cpu_unassigned_access()
> is a no-op for Alpha.

Oops.

> Make the MemoryRegionOps callbacks use the read_with_attrs
> and write_with_attrs hooks, so they can signal a failure
> that should cause a CPU exception by returning MEMTX_ERROR.
> 
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> RFC because untested, since I don't have an alpha test image.
> 
>  hw/alpha/typhoon.c | 47 ++++++++++++++++++++++++++--------------------
>  1 file changed, 27 insertions(+), 20 deletions(-)

Tested-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>

and queued.  Thanks.


r~

      reply	other threads:[~2018-12-10 18:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 17:33 [Qemu-devel] [RFC] hw/alpha/typhoon: Stop calling cpu_unassigned_access() Peter Maydell
2018-12-10 18:14 ` Richard Henderson [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=4271875c-faeb-ca7f-413c-df085b4a7da6@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=patches@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).