From: David Vrabel <david.vrabel@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] x86/xen: resume timer irqs early
Date: Fri, 8 Aug 2014 11:41:03 +0100 [thread overview]
Message-ID: <53E4A93F.6030704@citrix.com> (raw)
In-Reply-To: <53E3B797.9060701@oracle.com>
On 07/08/14 18:29, Boris Ostrovsky wrote:
> On 08/07/2014 01:16 PM, David Vrabel wrote:
>> If the timer irqs are resumed during device resume it is possible in
>> certain circumstances for the resume to hang early on, before device
>> interrupts are resumed.
>>
>> It is not entirely clear what is occuring the point of the hang but I
>> think a task necessary for the resume calls schedule_timeout(),
>> waiting for a timer interrupt (which never arrives). This failure may
>> require specific tasks to be running on the other VCPUs to trigger
>> (processes are not frozen during a suspend/resume if PREEMPT is
>> disabled).
>>
>> Add IRQF_EARLY_RESUME to the timer interrupts so they are resumed in
>> syscore_resume().
>>
>> Also add IRQF_NO_SUSPEND as it is not necessary to suspend the timer
>> interrupts and IRQF_FORCE_RESUME was already set.
>
>
> IRQF_NO_SUSPEND is a component of IRQF_TIMER.
So it is. How about this instead?
8<----------------------------
x86/xen: resume timer irqs early
If the timer irqs are resumed during device resume it is possible in
certain circumstances for the resume to hang early on, before device
interrupts are resumed.
It is not entirely clear what is occuring the point of the hang but I
think a task necessary for the resume calls schedule_timeout(),
waiting for a timer interrupt (which never arrives). This failure may
require specific tasks to be running on the other VCPUs to trigger
(processes are not frozen during a suspend/resume if PREEMPT is
disabled).
Add IRQF_EARLY_RESUME to the timer interrupts so they are resumed in
syscore_resume().
Signed-off-by: David Vrabel <david.vrabel@citrix.com>
---
arch/x86/xen/time.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/xen/time.c b/arch/x86/xen/time.c
index 7b78f88..5718b0b 100644
--- a/arch/x86/xen/time.c
+++ b/arch/x86/xen/time.c
@@ -444,7 +444,7 @@ void xen_setup_timer(int cpu)
irq = bind_virq_to_irqhandler(VIRQ_TIMER, cpu, xen_timer_interrupt,
IRQF_PERCPU|IRQF_NOBALANCING|IRQF_TIMER|
- IRQF_FORCE_RESUME,
+ IRQF_FORCE_RESUME|IRQF_EARLY_RESUME,
name, NULL);
(void)xen_set_irq_priority(irq, XEN_IRQ_PRIORITY_MAX);
--
1.7.10.4
next prev parent reply other threads:[~2014-08-08 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 17:16 [PATCH] x86/xen: resume timer irqs early David Vrabel
2014-08-07 17:29 ` Boris Ostrovsky
2014-08-08 10:41 ` David Vrabel [this message]
2014-08-08 14:04 ` Boris Ostrovsky
2014-08-08 14:35 ` David Vrabel
2014-08-08 17:15 ` Konrad Rzeszutek Wilk
2014-08-08 17:38 ` David Vrabel
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=53E4A93F.6030704@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).