From: Marc Zyngier <maz@kernel.org>
To: Tom Rini <trini@konsulko.com>
Cc: "Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>,
u-boot@lists.denx.de, Will Deacon <willdeacon@google.com>
Subject: Re: [PATCH 1/2] arm: cpu: Add optional CMOs by VA
Date: Tue, 07 Feb 2023 17:06:39 +0000 [thread overview]
Message-ID: <86pmalz9pc.wl-maz@kernel.org> (raw)
In-Reply-To: <Y+J+5eVwTS8cygn6@bill-the-cat>
On Tue, 07 Feb 2023 16:40:05 +0000,
Tom Rini <trini@konsulko.com> wrote:
>
> On Tue, Feb 07, 2023 at 04:35:25PM +0000, Marc Zyngier wrote:
> > On 2023-02-07 16:20, Ying-Chun Liu (PaulLiu) wrote:
> > > Exposing set/way cache maintenance to a virtual machine is unsafe, not
> > > least because the instructions are not permission-checked but also
> > > because they are not broadcast between CPUs. Consequently, KVM traps and
> > > emulates such maintenance in the host kernel using by-VA operations and
> > > looping over the stage-2 page-tables. However, when running under
> > > protected KVM, these instructions are not able to be emulated and will
> > > instead result in an exception being delivered to the guest.
> > >
> > > Introduce CONFIG_CMO_BY_VA_ONLY so that virtual platforms can select
> > > this option and perform by-VA cache maintenance instead of using the
> > > set/way instructions.
> > >
> > > Signed-off-by: Ying-Chun Liu (PaulLiu) <paul.liu@linaro.org>
> > > Signed-off-by: Marc Zyngier <maz@kernel.org>
> > > Signed-off-by: Will Deacon <willdeacon@google.com>
> > > Cc: Tom Rini <trini@konsulko.com>
> >
> > The sign-off chain looks pretty odd. Either you are the author
> > of this patch, and I have nothing to do on the sign-off list,
> > or I'm the author and the authorship is wrong. Similar things
> > would apply for Will.
> >
> > So which one is it?
>
> As my first guess here is copy and adopting code from Linux, this is
> not following the documented procedure here:
> https://u-boot.readthedocs.io/en/latest/develop/sending_patches.html#attributing-code-copyrights-signing
>
> Which if not sufficiently clear, please ask / suggest changes to. I see
> right now it isn't specific about cc'ing the original authors (who may,
> or may not, be interested, so blanket policy doesn't apply) but I would
> hope is clear enough that what's done in this example isn't right.
No, this really is u-boot code written as part of Android, from where
the patch has been directly lifted[1].
Same goes for Pierre-Clement's patch that is part of the same series.
I'm not overly attached to this code (I have bad memories from it),
but I think the OP may be unaware of these rules. In any case, I'm
supportive of this code making it in upstream u-boot. I just want it
to be done correctly.
Thanks,
M.
[1] https://android.googlesource.com/platform/external/u-boot/+/db5507f47f4f57f766d52f753ff2cc761afc213b
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2023-02-07 17:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 16:20 [PATCH 0/2] arm: cpu: Add optional CMOs by VA Ying-Chun Liu (PaulLiu)
2023-02-07 16:20 ` [PATCH 1/2] " Ying-Chun Liu (PaulLiu)
2023-02-07 16:35 ` Marc Zyngier
2023-02-07 16:40 ` Tom Rini
2023-02-07 17:06 ` Marc Zyngier [this message]
2023-02-07 17:12 ` Tom Rini
2023-02-07 17:18 ` Paul Liu
2023-02-08 8:20 ` Marc Zyngier
2023-02-07 16:20 ` [PATCH 2/2] arm64: Initialize TLB memory if CMO_BY_VA_ONLY Ying-Chun Liu (PaulLiu)
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=86pmalz9pc.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=paul.liu@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=willdeacon@google.com \
/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