All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kinzler <ml-xen-devel@hfp.de>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"JBeulich@novell.com" <JBeulich@novell.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Instability with Xen, interrupt routing frozen, HPET broadcast
Date: Thu, 30 Sep 2010 11:42:54 +0200	[thread overview]
Message-ID: <4CA45B9E.1060608@hfp.de> (raw)
In-Reply-To: <BC00F5384FCFC9499AF06F92E8B78A9E1A90A388F5@shsmsx502.ccr.corp.intel.com>

On 30.09.2010 07:00, Zhang, Xiantao wrote:
> Maybe you can disable pirq_set_affinity to have a try with the following patch.
 > It may trigger IRQ migration in hypervisor, and the IRQ migration 
logic about(especailly shared)
 > level-triggered ioapic IRQ is not well tested because of
 > no users before. After intoducing the pirq_set_affinity in
 > #Cset21625, the logic is used frequently when vcpu migration occurs

I am using Xen 4.0.1 which is c/s 21324 so I should not be affected?

 > Besides, there is a bug in event driver which is fixed in latest
 > pv_ops dom0, seems the dom0 you are using doesn't include the fix.
 > This bug may result in lost event in dom0 and invoke dom0
 > hang eventually.

Hmm, this really does not explain why everything is rock solid after 
disabling HPET broadcast? And the problem occured with every kernel 
(xenfied, pvops, all versions). Please correct me if I am wrong.

 > To workaround this bug,  you can disable irqbalance in dom0. Good luck!

As far as I know I am not using irq balancing (certainly not using the 
irqbalance daemon).

Regards Andreas

  parent reply	other threads:[~2010-09-30  9:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09  9:20 Instability with Xen, interrupt routing frozen, HPET broadcast Andreas Kinzler
2010-09-21 11:56 ` Pasi Kärkkäinen
2010-09-29 18:08   ` Andreas Kinzler
2010-09-29 19:34     ` Andrew Lyon
2010-09-29 21:18       ` Konrad Rzeszutek Wilk
2010-09-29 19:50     ` Jeremy Fitzhardinge
2010-09-30 10:16       ` Andreas Kinzler
2010-09-30 17:12         ` Jeremy Fitzhardinge
2010-09-30  5:00     ` Zhang, Xiantao
2010-09-30  6:02       ` Wei, Gang
2010-09-30  9:42       ` Andreas Kinzler [this message]
2010-10-01  4:14         ` Zhang, Xiantao
2010-12-31 14:31 ` Pasi Kärkkäinen
2011-01-09 19:10   ` Andreas Kinzler
2011-01-09 19:21     ` Pasi Kärkkäinen
2011-01-09 20:04       ` Keir Fraser
2011-01-19 10:19         ` Andreas Kinzler
  -- strict thread matches above, loose matches on Subject: below --
2011-05-04 22:31 Langsdorf, Mark
2011-05-05  6:27 ` Wei, Gang
2011-05-05 14:53   ` Langsdorf, Mark

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=4CA45B9E.1060608@hfp.de \
    --to=ml-xen-devel@hfp.de \
    --cc=JBeulich@novell.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xiantao.zhang@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.