mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Andi Kleen <ak@suse.de>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Dave Jones <davej@redhat.com>,
	Alan Cox <alan@redhat.com>
Subject: Re: [PATCH] lockless MCE i386 port
Date: Sun, 14 Nov 2004 09:54:26 +0100	[thread overview]
Message-ID: <20041114085426.GE16795@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0411130627050.3062@musoma.fsmlabs.com>

> +#define MCE_LOG_LEN 32
> +#define MCE_OVERFLOW 0		/* bit 0 in flags means overflow */
> +#define MCE_LOG_SIGNATURE	"MACHINECHECK"
> +#define MCE_GET_RECORD_LEN	_IOR('M', 1, int)
> +#define MCE_GET_LOG_LEN		_IOR('M', 2, int)
> +#define MCE_GETCLEAR_FLAGS	_Io


Just noticed this: 

First I think it would be better if you used the same format
(with u64) as x86-64 because this is a user visible interface,
and we get problems with 32bit emulation if it's too different.

Also it would allow to share the mcelog.c codebase.

> +
> +struct mce {
> +	u64 tsc;	/* cpu timestamp counter */
> +	u32 stsl;
> +	u32 stsh;
> +	u32 miscl;
> +	u32 misch;
> +	u32 addrl;
> +	u32 addrh;
> +	u32 mcgstl;
> +	u32 mcgsth;
> +	u32 eip;
> +	u8  cs;		/* code segment */
> +	u8  bank;	/* machine check bank */
> +	u8  cpu;	/* cpu that raised the error */
> +	u8  finished;	/* entry is valid */
> +	void *ext_arg;	/* extended feature arg */

A pointer? That doesn't make sense. This record must 
be self contained because it is passed by read() 

-Andi

  parent reply	other threads:[~2004-11-14  8:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-12 16:37 Zwane Mwaikambo
2004-11-13 18:36 ` Zwane Mwaikambo
2004-11-14  8:51   ` Andi Kleen
2004-11-15  1:10     ` Zwane Mwaikambo
2004-11-14  8:54   ` Andi Kleen [this message]
2004-11-15  1:40     ` Zwane Mwaikambo

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=20041114085426.GE16795@wotan.suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=alan@redhat.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linuxpower.ca \
    /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

all inboxes | Powered by JetHome®