On Thu, Feb 18, 2016 at 11:19:42AM +0100, Ingo Molnar wrote:
> > I think the whole notion of mcsafe here is 'wrong'. This copy variant
> > simply
> > reports the kind of trap that happened (#PF or #MC) and could arguably be
> > extended to include more types if the hardware were to generate more.
It is safe in the sense that when you get an MCE while shuffling data
here, in the kernel, you don't die but you recover. Thus the exception
handling games.
So _safe() really sounds fitting here.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
