public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Nowicki <tomasz.nowicki@linaro.org>
To: Borislav Petkov <bp@alien8.de>,
	Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linaro-acpi <linaro-acpi@lists.linaro.org>,
	Tony <tony.luck@intel.com>, Borislav Petkov <bp@suse.de>,
	linux-edac@vger.kernel.org, x86@kernel.org
Subject: Re: RFC: APEI hardware reduced profile
Date: Thu, 27 Mar 2014 10:17:56 +0100	[thread overview]
Message-ID: <5333ECC4.5080208@linaro.org> (raw)
In-Reply-To: <20140326203650.GA3933@nazgul.tnic>

On 03/26/14 21:36, Borislav Petkov wrote:
> On Wed, Mar 26, 2014 at 12:10:47PM -0300, Mauro Carvalho Chehab wrote:
>> Yet, it would be better if you could be a little more specific about
>> what are your plans and what are the common/not-common features that
>> you're mapping.
>
> Well, I don't see anything x86-specific in ghes.c on a quick scan - just
> the GHES gunk itself, which is the spec. Which begs the question, how
> much of the APEI spec is ARM going to implement and if it is a subset,
> this definitely needs to be handled cleanly. Judging by your text, it
> seems like you want to ignore the correctable errors part...?
>
> So yes, Tomasz, you want to be much more specific here :-)

Thanks for your comment. Please refer to my email to Mauro. I have put 
more explanation there.

Correctable errors are fine for ARM. But ARM is not going to have NMI 
ever. So as responded to Mauro, I am focusing on making NMI as the 
feature for ghes.c.

Thanks,
Tomasz

  reply	other threads:[~2014-03-27  9:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26 12:08 RFC: APEI hardware reduced profile Tomasz Nowicki
2014-03-26 14:55 ` Rafael J. Wysocki
2014-03-26 15:10   ` Mauro Carvalho Chehab
2014-03-26 20:36     ` Borislav Petkov
2014-03-27  9:17       ` Tomasz Nowicki [this message]
2014-03-27  9:05     ` Tomasz Nowicki

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=5333ECC4.5080208@linaro.org \
    --to=tomasz.nowicki@linaro.org \
    --cc=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=lenb@kernel.org \
    --cc=linaro-acpi@lists.linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=rjw@rjwysocki.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox