lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150601193733.GB17187@pd.tnic>
Date:	Mon, 1 Jun 2015 21:37:33 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	"Raj, Ashok" <ashok.raj@...el.com>
Cc:	linux-kernel@...r.kernel.org, linux-edac@...r.kernel.org,
	Borislav Petkov <bp@...e.de>, Tony Luck <tony.luck@...el.com>
Subject: Re: [Patch V1 2/3] x86, mce: Add infrastructure required to support
 LMCE

On Mon, Jun 01, 2015 at 11:48:57AM -0700, Raj, Ashok wrote:
> If you got a blank email, sorry about that. Its been a while since i used
> mutt and my setup was goofed up probably. Or i might have read your 
> signature a bit too literally :-)

LOL.

> I did re-organize this to read better in my upcoming post. But in
> general reading FEATURE_CONTROL isn't bad. It wont trip on a #GP for
> e.g. FEATURE_CONTROL has been around for a while.

Are you sure? Have you checked booting on qemu+kvm too?

I mean, I'm fine with whatever MSR access ordering we do as long as
nothing breaks. Obviously.

> Good point. Its required by architecture, since it depends on recovery
> support in processors to work. I forgot to add that to the SDM when
> i made those updates. I will update the SDM appropriately on my next
> attempt at it.

Ok, cool. Please add this fact to the commit message too.

> Sorry about my config challenges.. hopefully this makes it out with
> all the responses :-)

No worries, looks good :-)

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ