linux-kernel - Re: [PATCH] irqchip/gic-v3-its: remove the shareability of ITS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJqh2TKZJd6iuVexYV0Usq1j_+cMK5x=AyEZEip7A6KpQz3-dg@mail.gmail.com>
Date:   Fri, 9 Dec 2022 21:37:47 +0800
From:   Harry Song <jundongsong1@...il.com>
To:     Marc Zyngier <maz@...nel.org>
Cc:     Sebastian Reichel <sebastian.reichel@...labora.com>,
        tglx@...utronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] irqchip/gic-v3-its: remove the shareability of ITS

Thank you again.

Harry

On Fri, Dec 9, 2022 at 7:13 PM Marc Zyngier <maz@...nel.org> wrote:
>
> On Fri, 09 Dec 2022 03:34:21 +0000,
> Harry Song <jundongsong1@...il.com> wrote:
> >
> > Thank you for your reply. I know these two links.
> > My email is to ask about the root cause of this bug.
> >
> > I would like to know whether the driver design of ITS requires that
> > the CPU and ITS must be in a shared domain. Such as using CCI in
> > chips;
>
> This problem has nothing to do with CCI or coherency. It has to do
> with how the GIC is plugged in the interconnect and what attributes it
> advertises.
>
>         M.
>

Wow, that's a great link:
https://lore.kernel.org/lkml/878s5i2qyw.wl-maz@kernel.org/

Many thanks for your detailed reply.
I got the answer I wanted to know, That was very helpful.

> --
> Without deviation from the norm, progress is not possible.

Thank you again,
Harry