From: Jeremy Fitzhardinge <jeremy@goop.org>
To: MaoXiaoyun <tinnycloud@hotmail.com>
Cc: xen devel <xen-devel@lists.xensource.com>, keir.fraser@eu.citrix.com
Subject: Re: Re: VM hung after running sometime
Date: Wed, 29 Sep 2010 09:12:07 -0700 [thread overview]
Message-ID: <4CA36557.4040706@goop.org> (raw)
In-Reply-To: <BAY121-W512F127F0819CA2E5DC3D2DA670@phx.gbl>
On 09/28/2010 11:01 PM, MaoXiaoyun wrote:
> Well， I just go throught the source of irqbalance, it shows that it
> balances the irq through
> updating /proc/irq/$irq/smp_affinity. That, in my understanding, set
> irq affinity is almost
> equal to irq migration.
Correct.
>
> I later find the NIC interrupt is not modified in dom0, so it is safe
> to set its affinity,
> but interrupt of xen event use handle_level_irq, set its affinity will
> subject to irq
> lost.
>
> Am I right?
I can't parse that sentence so I'm not sure. But if you have
successfully migrated the interrupt/evtchn to a different vcpu, then
there's no subsequent risk of lost events. The event loss can only
happen in the circumstance I mentioned earlier: when you migrate while
an event is being handled, and a second event occurs on the new cpu
before the first one has finished. So you need both bad timing and a
fairly high event delivery rate to trigger the problem.
J
next prev parent reply other threads:[~2010-09-29 16:12 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY121-W45A47AC73BDA1A9E7474A2DA720@phx.gbl>
[not found] ` <C8ACD97B.1256D%keir.fraser@eu.citrix.com>
2010-09-10 11:01 ` VM hung after running sometime MaoXiaoyun
2010-09-19 10:37 ` MaoXiaoyun
2010-09-19 11:49 ` Keir Fraser
2010-09-19 12:21 ` Zhang, Yang Z
2010-09-20 6:00 ` MaoXiaoyun
2010-09-20 7:45 ` Keir Fraser
2010-09-20 8:23 ` MaoXiaoyun
2010-09-20 9:15 ` MaoXiaoyun
2010-09-20 9:35 ` Keir Fraser
2010-09-21 5:02 ` MaoXiaoyun
2010-09-21 7:53 ` Keir Fraser
2010-09-21 9:24 ` wei song
2010-09-21 9:49 ` wei song
2010-09-21 17:28 ` Jeremy Fitzhardinge
2010-09-22 0:02 ` MaoXiaoyun
2010-09-22 0:17 ` Jeremy Fitzhardinge
2010-09-22 1:19 ` MaoXiaoyun
2010-09-22 18:31 ` Jeremy Fitzhardinge
2010-09-23 0:55 ` MaoXiaoyun
2010-09-23 23:20 ` Jeremy Fitzhardinge
2010-09-24 4:29 ` MaoXiaoyun
2010-09-25 9:33 ` MaoXiaoyun
2010-09-25 10:40 ` wei song
2010-09-27 18:02 ` Jeremy Fitzhardinge
2010-09-27 11:56 ` MaoXiaoyun
2010-09-28 5:43 ` MaoXiaoyun
2010-09-28 11:23 ` MaoXiaoyun
2010-09-28 17:07 ` Jeremy Fitzhardinge
2010-09-29 6:01 ` MaoXiaoyun
2010-09-29 16:12 ` Jeremy Fitzhardinge [this message]
2010-10-15 12:43 ` Domain 0 stop response on frequently reboot VMS MaoXiaoyun
2010-10-15 12:57 ` Keir Fraser
2010-10-16 5:39 ` MaoXiaoyun
2010-10-16 7:16 ` Keir Fraser
2010-10-18 21:17 ` Daniel Stodden
2010-10-24 5:48 ` MaoXiaoyun
2010-10-24 5:56 ` Daniel Stodden
2010-10-26 8:16 ` MaoXiaoyun
2010-10-26 9:09 ` Daniel Stodden
2010-10-26 10:54 ` MaoXiaoyun
2010-10-26 9:20 ` Ian Campbell
2010-10-26 10:59 ` MaoXiaoyun
2010-10-26 11:54 ` Domain 0 stop response on frequently reboot VMS, fix xen/master link? Pasi Kärkkäinen
2010-10-26 17:08 ` Jeremy Fitzhardinge
2010-11-04 3:09 ` A Patch for modify DomU network transmit rate dynamically MaoXiaoyun
2010-11-04 3:43 ` MaoXiaoyun
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=4CA36557.4040706@goop.org \
--to=jeremy@goop.org \
--cc=keir.fraser@eu.citrix.com \
--cc=tinnycloud@hotmail.com \
--cc=xen-devel@lists.xensource.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.