From: "Liu, Chuansheng" <chuansheng.liu@intel.com>
To: Boris Petkov <bp@alien8.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Luck, Tony" <tony.luck@intel.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>
Subject: RE: [PATCH] x86/mce/therm_throt: Fix the access of uninitialized therm_work
Date: Mon, 6 Jan 2020 10:10:11 +0000 [thread overview]
Message-ID: <27240C0AC20F114CBF8149A2696CBE4A615FC376@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <130561C3-5E52-4693-B15F-B89C8B8366B0@alien8.de>
> -----Original Message-----
> From: Boris Petkov <bp@alien8.de>
> Sent: Monday, January 6, 2020 6:01 PM
> To: Liu, Chuansheng <chuansheng.liu@intel.com>
> Cc: linux-kernel@vger.kernel.org; Luck, Tony <tony.luck@intel.com>;
> tglx@linutronix.de; mingo@redhat.com; hpa@zytor.com
> Subject: RE: [PATCH] x86/mce/therm_throt: Fix the access of uninitialized
> therm_work
>
> On January 6, 2020 10:22:06 AM GMT+01:00, "Liu, Chuansheng"
> <chuansheng.liu@intel.com> wrote:
> >I traced there is about 2s gap between unmask interrupt and workqueue
> >Initialization.
>
> And that is a problem because?
>
> You setup workqueue etc and *then* unmask the irq.
>
Some previous experience shows:
If there is critical thermal alert, we still can take action in kernel side in this
2s, even though the workqueue is not ready, but interrupt handler can work
well.
next prev parent reply other threads:[~2020-01-06 10:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 6:41 Chuansheng Liu
2020-01-06 7:07 ` Borislav Petkov
2020-01-06 7:11 ` Ingo Molnar
2020-01-06 9:24 ` Liu, Chuansheng
2020-01-11 4:20 ` Liu, Chuansheng
2020-01-06 9:22 ` Liu, Chuansheng
2020-01-06 10:01 ` Boris Petkov
2020-01-06 10:10 ` Liu, Chuansheng [this message]
2020-01-06 10:37 ` Boris Petkov
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=27240C0AC20F114CBF8149A2696CBE4A615FC376@SHSMSX101.ccr.corp.intel.com \
--to=chuansheng.liu@intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®