All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengzhe Zhang <fengzhe.zhang@intel.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	xen-devel <xen-devel@lists.xensource.com>,
	"Dong, Eddie" <eddie.dong@intel.com>,
	"Li, Xin" <xin.li@intel.com>
Subject: Re: [PATCH] irq: Exclude percpu IRQs from being fixed up
Date: Thu, 17 Feb 2011 08:15:43 +0800	[thread overview]
Message-ID: <4D5C68AF.3030807@intel.com> (raw)
In-Reply-To: <4D5BF2FE02000078000322EB@vpn.id2.novell.com>

On 2011/2/16 22:53, Jan Beulich wrote:
>>>> On 16.02.11 at 15:26, "Zhang, Fengzhe"<fengzhe.zhang@intel.com>  wrote:
>> irq: Exclude percpu IRQs from being fixed up
>>
>> Xen spin unlock uses spurious ipi "lock_kicker_irq" to wake up blocked vCPUs
>> waiting on that lock. This irq should always be disabled. However, when Dom0
>> is shuting down, function fixup_irqs is called which unmasks all irqs.
>> Function unmask_irq effectively re-enables lock_kicker_irq and its irq handler
>> is invoked which reports bug and crashes Dom0.
>>
>> This patch sets IRQ_PER_CPU flag in irq desc and excludes percpu IRQs from
>> being fixed up when taking CPUs down.
>>
>> Signed-off-by: Fengzhe Zhang<fengzhe.zhang@intel.com>
>>
>> diff --git a/arch/x86/kernel/irq_64.c b/arch/x86/kernel/irq_64.c
>> index 977d8b4..f0f9450 100644
>> --- a/arch/x86/kernel/irq_64.c
>> +++ b/arch/x86/kernel/irq_64.c
>> @@ -80,6 +80,9 @@ void fixup_irqs(void)
>>   		if (irq == 2)
>>   			continue;
>>
>> +		if (desc->status&  IRQ_PER_CPU)
>> +			continue;
>> +
>>   		/* interrupt's are disabled at this point */
>>   		spin_lock(&desc->lock);
>>
>> diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
>> index f34e231..26bc55a 100644
>> --- a/kernel/irq/manage.c
>> +++ b/kernel/irq/manage.c
>> @@ -727,10 +727,9 @@ __setup_irq(unsigned int irq, struct irq_desc *desc,
>> struct irqaction *new)
>>   				goto out_thread;
>>   		} else
>>   			compat_irq_chip_set_default_handler(desc);
>> -#if defined(CONFIG_IRQ_PER_CPU)
>
> Why? XEN should select IRQ_PER_CPU instead in its Kconfig.
>
> Jan
>
IRQ_PER_CPU switch is not found in current Kconfig. I'm not sure if this 
feature is going to be brought back in the short term. I remove the 
ifdef to set IRQ_PER_CPU flag in desc by default but still leave the IRQ 
handling logic unchanged. This is a temporary solution to fix system 
crash on poweroff. And this is the fix with minimum impact among the 
several solutions we tried.

-Fengzhe

>> +
>>   		if (new->flags&  IRQF_PERCPU)
>>   			desc->status |= IRQ_PER_CPU;
>> -#endif
>>
>>   		desc->status&= ~(IRQ_AUTODETECT | IRQ_WAITING | IRQ_ONESHOT |
>>   				  IRQ_INPROGRESS | IRQ_SPURIOUS_DISABLED);
>
>

  reply	other threads:[~2011-02-17  0:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16 14:26 [PATCH] irq: Exclude percpu IRQs from being fixed up Zhang, Fengzhe
2011-02-16 14:53 ` Jan Beulich
2011-02-17  0:15   ` Fengzhe Zhang [this message]
2011-02-17  7:52     ` Jan Beulich
2011-02-17  8:25       ` Fengzhe Zhang
2011-04-28 11:05         ` Li, Xin
2011-05-03 11:55           ` Ian Campbell
2011-02-17  9:09       ` Ian Campbell
2011-05-05  6:55         ` Tian, Kevin

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=4D5C68AF.3030807@intel.com \
    --to=fengzhe.zhang@intel.com \
    --cc=JBeulich@novell.com \
    --cc=eddie.dong@intel.com \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=xin.li@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.