linux-kernel - Re: [PATCH] Intel Management Engine Interface

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 11 Dec 2007 19:14:31 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Anas Nashif <nashif@...ux.intel.com>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] Intel Management Engine Interface

Anas Nashif <nashif@...ux.intel.com> writes:
>
> The Intel Management Engine Interface (aka HECI: Host Embedded 
> Controller Interface ) enables communication between the host OS and 
> the Management Engine firmware. MEI is bi-directional, and either the 
> host or Intel AMT firmware can initiate transactions.

Can you please expand a bit on who on the host OS would actually communicate
with the management engine? It looks like this driver just exports
an interface to user space. What user space would use it and for
what?

I would be definitely interested in a way to save oops information
away using this.  I remember you had a demo for this, is support
for that coming soon?

-Andi
--
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/