From: Oleg Nesterov <oleg@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, "Chen,
Gong" <gong.chen@linux.intel.com>,
tony.luck@intel.com, x86@kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: [PATCH v2 4/5] x86/mce: Simplify flow when handling recoverable memory errors
Date: Wed, 12 Nov 2014 18:20:58 +0100 [thread overview]
Message-ID: <20141112172057.GA8303@redhat.com> (raw)
In-Reply-To: <20141111114248.GD31490@pd.tnic>
Sorry, I am a bit confused...
On 11/11, Borislav Petkov wrote:
>
> Roughly speaking, we want to be able to mark a task with the sign of
> death and to kill it, if needed.
"it" is current, yes?
So I agree with Andy, task_work_add() can work and you can also pass
paddr/restartable to the handler.
But,
> The important part is *before* it
> gets to run again.
But it is already running? Perhaps you meant "before it returns to
user-mode" ?
Oleg.
next prev parent reply other threads:[~2014-11-12 17:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 6:49 x86, MCE: MCE event ring management Chen, Gong
2014-08-14 6:49 ` [PATCH v2 1/5] x86, MCE: Provide a lock-less memory pool to save error record Chen, Gong
2014-08-14 6:49 ` [PATCH v2 2/5] x86, MCE: Don't use percpu for MCE workqueue/irq_work Chen, Gong
2014-08-14 6:49 ` [PATCH v2 3/5] x86, MCE: Remove mce_ring for SRAO error Chen, Gong
2014-08-14 6:49 ` [PATCH v2 4/5] x86/mce: Simplify flow when handling recoverable memory errors Chen, Gong
2014-11-11 11:42 ` Borislav Petkov
2014-11-11 15:42 ` Andy Lutomirski
2014-11-11 16:13 ` Borislav Petkov
2014-11-11 16:22 ` Andy Lutomirski
2014-11-11 16:30 ` Borislav Petkov
2014-11-11 17:15 ` Andy Lutomirski
2014-11-11 18:22 ` Borislav Petkov
2014-11-11 18:34 ` Andy Lutomirski
2014-11-11 18:38 ` Borislav Petkov
2014-11-11 20:10 ` Andy Lutomirski
2014-11-12 17:20 ` Oleg Nesterov [this message]
2014-11-12 17:25 ` Andy Lutomirski
2014-11-12 17:27 ` Borislav Petkov
2014-08-14 6:49 ` [PATCH v2 5/5] x86, MCE: Avoid potential deadlock in MCE context Chen, Gong
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=20141112172057.GA8303@redhat.com \
--to=oleg@redhat.com \
--cc=bp@alien8.de \
--cc=gong.chen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=peterz@infradead.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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.