From: Peter Maydell <peter.maydell@linaro.org>
To: eric.auger@redhat.com
Cc: eric.auger.pro@gmail.com, richard.henderson@linaro.org,
pbonzini@redhat.com, qemu-devel@nongnu.org, philmd@linaro.org
Subject: Re: [PATCH v3] target/arm: Add raw_writes ops for register whose write induce TLB maintenance
Date: Tue, 27 Jun 2023 13:23:17 +0100 [thread overview]
Message-ID: <CAFEAcA_y2WHGU8xQ0Tw-UfdXF-FPbAV=mHA0vHYzoSz66VBoJQ@mail.gmail.com> (raw)
In-Reply-To: <27fd657b-02e7-658c-4cc4-07a6c374a1b9@redhat.com>
On Fri, 23 Jun 2023 at 17:43, Eric Auger <eric.auger@redhat.com> wrote:
>
> Hi Peter,
>
> On 2/28/23 10:36, Eric Auger wrote:
> > Some registers whose 'cooked' writefns induce TLB maintenance do
> > not have raw_writefn ops defined. If only the writefn ops is set
> > (ie. no raw_writefn is provided), it is assumed the cooked also
> > work as the raw one. For those registers it is not obvious the
> > tlb_flush works on KVM mode so better/safer setting the raw write.
> >
> > Signed-off-by: Eric Auger <eric.auger@redhat.com>
> > Suggested-by: Peter Maydell <peter.maydell@linaro.org>
>
> If I am not wrong this patch fell into the cracks. Is it in a decent
> state now?
Oops, sorry about that. Yes, I think v3 looks good; I've
applied it to target-arm.next.
thanks
-- PMM
next prev parent reply other threads:[~2023-06-27 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 9:36 [PATCH v3] target/arm: Add raw_writes ops for register whose write induce TLB maintenance Eric Auger
2023-06-23 16:43 ` Eric Auger
2023-06-27 12:23 ` Peter Maydell [this message]
2023-06-27 12:24 ` Eric Auger
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='CAFEAcA_y2WHGU8xQ0Tw-UfdXF-FPbAV=mHA0vHYzoSz66VBoJQ@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=pbonzini@redhat.com \
--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).