From: David Vrabel <david.vrabel@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH] x86/xen: resume timer irqs early
Date: Fri, 8 Aug 2014 18:38:43 +0100 [thread overview]
Message-ID: <53E50B23.5080200@citrix.com> (raw)
In-Reply-To: <20140808171502.GG13551@laptop.dumpdata.com>
On 08/08/14 18:15, Konrad Rzeszutek Wilk wrote:
> On Fri, Aug 08, 2014 at 03:35:27PM +0100, David Vrabel wrote:
>> On 08/08/14 15:04, Boris Ostrovsky wrote:
>>> On 08/08/2014 06:41 AM, David Vrabel wrote:
>>>> 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?
>>>
>>> The change makes sense so
>>>
>>> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>>>
>>> but I am curious whether you actually were able to prove that it in fact
>>> fixes the hang (the description doesn't make it clear).
>>
>> Without the patch repeatedly migrating a VM would hang during resume
>> after < 500 iterations. With the patch the VM was migrated > 8000 times
>> without a problem.
>
> Ah, should said patch have a Reported-by too then?
I don't think the XenServer automated test system really minds.
> It would also be neat to have that in the description of the patch I think.
I'm not really keen on system-specific numbers like this, but it would
probably be useful in this case since my analysis is so woolly.
David
prev parent reply other threads:[~2014-08-08 17:38 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
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 [this message]
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=53E50B23.5080200@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=konrad.wilk@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).