From: "Luck, Tony" <tony.luck@intel.com>
To: Tyler Hicks <tyhicks@linux.microsoft.com>,
Borislav Petkov <bp@alien8.de>
Cc: wangglei <wangglei@gmail.com>,
"Lei Wang (DPLAT)" <Wang.Lei@microsoft.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"james.morse@arm.com" <james.morse@arm.com>,
"rric@kernel.org" <rric@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Hang Li <hangl@microsoft.com>,
Brandon Waller <bwaller@microsoft.com>
Subject: RE: [EXTERNAL] Re: [PATCH] EDAC: update edac printk wrappers to use printk_ratelimited.
Date: Wed, 5 May 2021 23:13:30 +0000 [thread overview]
Message-ID: <d727342c294b4d40b411dc25cbd3266f@intel.com> (raw)
In-Reply-To: <20210505230152.GH4967@sequoia>
>> What is your situation? ARM?
>
> Yes, though I'm not sure if those additional features are
> important/useful enough for us to generalize that driver. The main
> motivation here was just to prevent storage/network from being flooded
> by obviously-bad nodes that haven't been offlined yet. :)
>
> Lei and others on cc will need to evaluate porting cec.c and what it
> will gain them. Thanks again.
Tyler,
You might also look at the x86 "storm" detection code (tl;dr version
"If error interrupts are coming too fast, turn off the interrupts and poll").
-Tony
next prev parent reply other threads:[~2021-05-05 23:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 17:30 [PATCH] EDAC: update edac printk wrappers to use printk_ratelimited Lei Wang
2021-05-05 18:01 ` Borislav Petkov
2021-05-05 19:02 ` [EXTERNAL] " Lei Wang (DPLAT)
2021-05-05 19:45 ` Borislav Petkov
2021-05-05 20:23 ` Tyler Hicks
2021-05-05 21:04 ` Borislav Petkov
2021-05-05 21:48 ` Tyler Hicks
2021-05-05 22:02 ` Borislav Petkov
2021-05-05 22:16 ` Tyler Hicks
2021-05-05 22:43 ` Tyler Hicks
2021-05-05 22:55 ` Borislav Petkov
2021-05-05 23:01 ` Tyler Hicks
2021-05-05 23:13 ` Luck, Tony [this message]
2021-05-06 7:16 ` Mauro Carvalho Chehab
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=d727342c294b4d40b411dc25cbd3266f@intel.com \
--to=tony.luck@intel.com \
--cc=Wang.Lei@microsoft.com \
--cc=bp@alien8.de \
--cc=bwaller@microsoft.com \
--cc=hangl@microsoft.com \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rric@kernel.org \
--cc=tyhicks@linux.microsoft.com \
--cc=wangglei@gmail.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 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.