All of lore.kernel.org
 help / color / mirror / Atom feed
From: bp@alien8.de (Borislav Petkov)
To: linux-arm-kernel@lists.infradead.org
Subject: EDAC driver for ARMv8 L1/L2 cache
Date: Tue, 9 Jan 2018 23:00:10 +0100	[thread overview]
Message-ID: <20180109220009.fgpp6n6c5r4hxihp@pd.tnic> (raw)
In-Reply-To: <VI1PR04MB20788AC2E71A3CFFC37B85BB9A100@VI1PR04MB2078.eurprd04.prod.outlook.com>

On Tue, Jan 09, 2018 at 09:51:32PM +0000, York Sun wrote:
> On 01/09/2018 01:43 PM, Borislav Petkov wrote:
> > Adding some more people to CC.
> > 
> > On Tue, Jan 09, 2018 at 08:48:43PM +0000, York Sun wrote:
> >> Borislav,
> >>
> >> Are you aware of any existing (or in development) EDAC driver for ARMv8
> >> L1/L2 cache? I am thinking to write one if not available yet.
> > 
> > no I'm not but I see two EDAC drivers for ARM64: thunderx and xgene.
> > 
> > Please synchronize with their authors and ARM people what would be the
> > best thing to do and try extracting shared functionality from them
> > into a common compilation unit instead of duplicating it. I don't want
> > separate drivers per functional unit.
> > 
> 
> Thanks for the pointer. Thunderx and xgene's drivers have different
> implementation on the hardware. I found one patch closer to what I
> expect, https://patchwork.kernel.org/patch/7513231/. I don't see
> activities after 2015. I will reach out to the author.

He's probably busy with SME/SEV right now.

+ Marc.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

  reply	other threads:[~2018-01-09 22:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <VI1PR04MB2078DBC9381EA574CE5DA4B09A100@VI1PR04MB2078.eurprd04.prod.outlook.com>
2018-01-09 21:43 ` EDAC driver for ARMv8 L1/L2 cache Borislav Petkov
2018-01-09 21:51   ` York Sun
2018-01-09 22:00     ` Borislav Petkov [this message]
2018-01-12 16:38     ` Thor Thayer
2018-01-12 16:48       ` York Sun
2018-01-12 17:12         ` Borislav Petkov
2018-01-12 17:17           ` York Sun
2018-01-12 17:38             ` Mark Rutland
2018-01-12 17:44               ` York Sun
2018-01-12 18:00                 ` Mark Rutland
2018-01-12 18:16                   ` York Sun
2018-01-13 11:31                     ` Borislav Petkov
2018-01-15 14:21                       ` Mark Rutland
2018-01-15 14:32                         ` Borislav Petkov
2018-01-15 14:49                           ` Mark Rutland
2018-01-15 16:19                           ` York Sun
2018-01-15 23:23                             ` Borislav Petkov
2018-01-15 23:28                               ` York Sun
2018-01-15 23:52                                 ` Borislav Petkov
2018-01-16  0:16                                   ` York Sun
2018-02-01 20:56                                   ` York Sun
2018-02-08 15:31                                     ` James Morse
2018-02-08 15:53                                       ` York Sun
2018-01-12 17:23           ` Mark Rutland
2018-01-12 17:39         ` Thor Thayer

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=20180109220009.fgpp6n6c5r4hxihp@pd.tnic \
    --to=bp@alien8.de \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.