public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <ak@linux.intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: x86/mce merge, integration hickup + crash, design thoughts
Date: Tue, 30 Dec 2008 07:50:08 +0100	[thread overview]
Message-ID: <20081230065008.GC30975@elte.hu> (raw)
In-Reply-To: <4959466F.5030205@linux.intel.com>


* Andi Kleen <ak@linux.intel.com> wrote:

> Ingo Molnar wrote:
>
>> today i (belatedly ...) started looking into the status of the 
>> tip/x86/mce branch, and merged it into tip/master as a first step.
>>
>> firstly there's a small complication, it triggers this crash with the  
>> attached config:
>>
>
> I tested the config on a couple of different systems. Unfortunately I 
> wasn't able to reproduce the problem. It booted always fine even on 
> multiple tries.
>
> I had to adapt the configuration slightly to boot in my setup.
>
> The configuration also was not complete, i had to press return a few 
> times (are you sure you sent me the correct file?)
>
> One merging issue I noted is that you put the perfctrs and mce self on 
> the same vector. The attached patch fixes that.

hm, will re-test and see whether i can get more debug info out of the 
system.

> commit c736d118dcad93929dfc21cb72f33bc94c1b314a
> Author: Andi Kleen <ak@linux.intel.com>
> Date:   Sun Dec 28 14:16:43 2008 +0100
> 
>     Avoid conflict of apic error and local perfmon vector
>     
>     Signed-off-by: Andi Kleen <ak@linux.intel.com>
> 
> diff --git a/arch/x86/include/asm/irq_vectors.h b/arch/x86/include/asm/irq_vectors.h
> index 73957a2..0fcb682 100644
> --- a/arch/x86/include/asm/irq_vectors.h
> +++ b/arch/x86/include/asm/irq_vectors.h
> @@ -88,7 +88,7 @@
>  /*
>   * Performance monitoring interrupt vector:
>   */
> -#define LOCAL_PERF_VECTOR	0xee
> +#define LOCAL_PERF_VECTOR	0xed

this reminds me, i dont particularly like the way you added a 
self-interrupt:

+       __send_IPI_shortcut(APIC_DEST_SELF, MCE_SELF_VECTOR, 0);

IPI self-sends are generally more fragile than task-flag based methods, 
and they also waste IRQ vector real-estate.

	Ingo

  reply	other threads:[~2008-12-30  6:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-27 15:50 x86/mce merge, integration hickup + crash, design thoughts Ingo Molnar
2008-12-27 22:51 ` Ingo Molnar
2008-12-29 21:41   ` Andi Kleen
2009-01-13 17:45     ` Ingo Molnar
2009-01-13 18:57       ` Tim Hockin
2009-01-14  9:29         ` Andi Kleen
2009-01-14 16:18           ` Tim Hockin
2009-01-14 18:05             ` Andi Kleen
2009-01-14 19:32               ` Tim Hockin
2009-01-15 22:56                 ` Andi Kleen
2009-01-15 23:39                   ` Tim Hockin
2009-01-14  2:02       ` Huang Ying
2008-12-30 21:13   ` Russ Anderson
2008-12-31 13:32     ` Andi Kleen
2008-12-31 18:09       ` Russ Anderson
2008-12-29 21:51 ` Andi Kleen
2008-12-30  6:50   ` Ingo Molnar [this message]
2008-12-30  9:13     ` Andi Kleen
2008-12-30 21:29 ` Russ Anderson
2009-01-12 22:02 ` Tim Hockin
2009-01-13  5:02   ` Andi Kleen

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=20081230065008.GC30975@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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