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
On 03/26/14 16:10, Mauro Carvalho Chehab wrote:
Em Wed, 26 Mar 2014 15:55:07 +0100
"Rafael J. Wysocki" escreveu:
On Wednesday, March 26, 2014 01:08:10 PM Tomasz Nowicki wrote:
Hi,
Hi,
This is a question for Tony, Boris and Mauro (CCed now).
Currently APEI depends on x86 architecture. It
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 -
Em Wed, 26 Mar 2014 15:55:07 +0100
"Rafael J. Wysocki" escreveu:
> On Wednesday, March 26, 2014 01:08:10 PM Tomasz Nowicki wrote:
> > Hi,
>
> Hi,
>
> This is a question for Tony, Boris and Mauro (CCed now).
>
> > Currently APEI depends on x86 architecture. It is because of many x86
> > specif
On Wednesday, March 26, 2014 01:08:10 PM Tomasz Nowicki wrote:
> Hi,
Hi,
This is a question for Tony, Boris and Mauro (CCed now).
> Currently APEI depends on x86 architecture. It is because of many x86
> specific features like "IA-32 Architecture Corrected Machine Check
> " error source or NMI
Hi,
Currently APEI depends on x86 architecture. It is because of many x86
specific features like "IA-32 Architecture Corrected Machine Check
" error source or NMI hardware error notification. However, many other
features like "PCI Express Device AER Structure" or GHES via external
interrupt ca
6 matches
Mail list logo
