mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Anas Nashif <nashif@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Intel Management Engine Interface
Date: Tue, 11 Dec 2007 19:14:31 +0100	[thread overview]
Message-ID: <p7363z5nlo8.fsf@bingen.suse.de> (raw)
In-Reply-To: <475EC9C1.9080708@linux.intel.com> (Anas Nashif's message of "Tue\, 11 Dec 2007 12\:32\:49 -0500")

Anas Nashif <nashif@linux.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

  reply	other threads:[~2007-12-11 18:14 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 17:32 Anas Nashif
2007-12-11 18:14 ` Andi Kleen [this message]
2007-12-11 18:38   ` Anas Nashif
2007-12-11 18:53     ` Andi Kleen
2007-12-11 19:02       ` David Miller
2007-12-11 19:47         ` Andi Kleen
2007-12-11 19:06       ` Anas Nashif
2007-12-11 19:48         ` Andi Kleen
2007-12-12 15:00         ` Mark Lord
2007-12-12 16:17           ` Andi Kleen
2007-12-12  8:48 ` Alexander E. Patrakov
2008-05-20  0:11 Anas Nashif
2008-05-20  0:28 ` Andrew Morton
2008-05-20 19:02   ` Gabriel C
2008-05-22 16:51   ` Pavel Machek
2008-05-20 15:42 ` Maxim Levitsky
2008-05-20 20:35 ` Carlos R. Mafra
2008-05-20 22:27 ` Jiri Slaby
2008-05-23  7:04 ` Pavel Machek
2008-07-17 18:27 Marcin Obara
2008-07-18  0:00 ` Randy Dunlap
2008-07-18  5:44 ` Marcin Obara
2008-07-18 17:39   ` Marcin Obara
2008-07-18 19:23     ` Marcin Obara
2008-07-18 20:30       ` Marcin Obara
2008-07-23 18:00         ` Marcin Obara
2008-08-11 19:23           ` Marcin Obara
2008-08-12  4:53             ` Andrew Morton
2008-08-12 16:15               ` Jiri Slaby
2008-08-12 19:24                 ` Marcin Obara
2008-08-12 19:24                   ` Alan Cox
2008-08-12 21:03                   ` Arjan van de Ven
2008-08-13  0:58             ` Greg KH
2008-08-13  7:16               ` Marcin Obara
2008-08-13 18:18                 ` Greg KH
2008-08-13 19:48                   ` Marcin Obara
2008-08-14  0:23                     ` Greg KH
2008-07-18  9:27 ` Andi Kleen
2008-07-18 10:51   ` Marcin Obara
2008-07-18 11:02     ` Andi Kleen
2008-07-18 11:33       ` Marcin Obara
2008-08-06 16:56 ` Pavel Machek

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=p7363z5nlo8.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nashif@linux.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
Powered by JetHome