From: M Bazz <bazz@bazz1.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Richard Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Artyom Tarasenko <atar4qemu@gmail.com>
Subject: Re: [PATCH] target/sparc: Use GET_ASI_CODE for ASI_KERNELTXT and ASI_USERTXT
Date: Fri, 12 Apr 2024 15:49:32 -0400 [thread overview]
Message-ID: <CAMFqb-afq2RwkKZx1kAeEFRf=VUhoUk_Nsp6NCDVWP-qfNZEHg@mail.gmail.com> (raw)
In-Reply-To: <921ae82a-3007-4435-af7d-91a08a5acae7@linaro.org>
Hi Philippe,
On Fri, Apr 12, 2024 at 7:14 AM Philippe Mathieu-Daudé
<philmd@linaro.org> wrote:
>
> Hi Bazz,
>
> On 12/4/24 06:18, M Bazz wrote:
> > On Thu, Apr 11, 2024, 10:15 PM Richard Henderson
> > <richard.henderson@linaro.org <mailto:richard.henderson@linaro.org>> wrote:
> >
> > Reads are done with execute access. It is not clear whether writes
> > are legal at all -- for now, leave helper_st_asi unchanged, so that
> > we continue to raise an mmu fault.
> >
> > This generalizes the exiting code for ASI_KERNELTXT to be usable for
> > ASI_USERTXT as well, by passing down the MemOpIdx to use.
> >
> > Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2281
> > <https://gitlab.com/qemu-project/qemu/-/issues/2281>
> > Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2059
> > <https://gitlab.com/qemu-project/qemu/-/issues/2059>
> > Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1609
> > <https://gitlab.com/qemu-project/qemu/-/issues/1609>
> > Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1166
> > <https://gitlab.com/qemu-project/qemu/-/issues/1166>
> > Signed-off-by: Richard Henderson <richard.henderson@linaro.org
> > <mailto:richard.henderson@linaro.org>>
> > ---
> > target/sparc/helper.h | 3 ++
> > target/sparc/ldst_helper.c | 65 ++++++++++++++++++++++++++------------
> > target/sparc/translate.c | 49 ++++++++++++++++++++++++++--
> > 3 files changed, 95 insertions(+), 22 deletions(-)
>
> > Hi Richard,
> >
> > I see this is in your hands now. I agree with your take on leaving
> > writes alone. I'm also grateful for the opportunity to collaborate with you.
> >
> > It brings a smile for the community members who will be touched by this
> > amazing contribution. I see them happily realizing that this perplexing
> > bug has been solved, and in our case finally able to use the debuggers
> > we love! :D
>
> Does that mean you tested this patch and it resolves your issues?
>
> If so, could you add your 'Tested-by: M Bazz <bazz@bazz1.com>' tag
> when committing this patch?
>
> Regards,
>
> Phil.
Yes, I can confirm the issue is resolved. Richard has already made the
pull request. I am appreciative of the fast movement on this.
I would like to have my "Tested-by" tag added to the PR, if it's no
trouble. How might I get it there?
Tested-by: M Bazz <bazz@bazz1.com>
>
> > Thanks for the proper fix, qemu sensei!
> >
> > -bazz
> >
>
next prev parent reply other threads:[~2024-04-12 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 2:15 [PATCH] target/sparc: Use GET_ASI_CODE for ASI_KERNELTXT and ASI_USERTXT Richard Henderson
2024-04-12 4:18 ` M Bazz
2024-04-12 11:14 ` Philippe Mathieu-Daudé
2024-04-12 19:49 ` M Bazz [this message]
2024-04-12 18:30 ` Mark Cave-Ayland
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='CAMFqb-afq2RwkKZx1kAeEFRf=VUhoUk_Nsp6NCDVWP-qfNZEHg@mail.gmail.com' \
--to=bazz@bazz1.com \
--cc=atar4qemu@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).