All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastian Blank <waldi@debian.org>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Fraser <keir.fraser@eu.citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: pvops-2.6.32 - Interrupt routing problem
Date: Fri, 19 Mar 2010 12:06:13 +0100	[thread overview]
Message-ID: <20100319110613.GA29006@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <EB8593BCECAB3D40A8248BE0B6400A384651FFBC@shzsmsx502.ccr.corp.intel.com>

On Fri, Mar 19, 2010 at 10:55:53AM +0800, Zhang, Xiantao wrote:
> Maybe we need allow dom0 to re-programme the first 15 GSIs to solve this issue.  And the root-cause is that the IRQ info(polarity&trigger mode) provided in MP table in some platforms is not always trusted, and system should re-programme it according to the info parsed from ACPI.  If the platform provide correct info in MP table, the issue should be gone.   Attached a proposed patch, could you have a try to see whether it can fix your issue.  

The outcome is exactly the same than
<20100316182053.GA2258@wavehammer.waldi.eu.org>. However it still
reports errors back to the domain.

Bastian

-- 
I'm a soldier, not a diplomat.  I can only tell the truth.
		-- Kirk, "Errand of Mercy", stardate 3198.9

  reply	other threads:[~2010-03-19 11:06 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10 11:19 pvops-2.6.32 - Interrupt routing problem Bastian Blank
2010-03-10 16:08 ` Ian Campbell
2010-03-10 16:19   ` Bastian Blank
2010-03-10 18:17     ` Jeremy Fitzhardinge
2010-03-10 20:32       ` Bastian Blank
2010-03-10 19:40     ` Ian Campbell
2010-03-10 20:00       ` Konrad Rzeszutek Wilk
2010-03-14 14:08 ` Bastian Blank
2010-03-14 15:23   ` Bastian Blank
2010-03-14 15:56     ` Jeremy Fitzhardinge
2010-03-14 16:17       ` Bastian Blank
2010-03-15  4:30         ` Zhang, Xiantao
2010-03-15 10:11           ` Bastian Blank
2010-03-15 10:36             ` Bastian Blank
2010-03-15 13:48             ` Zhang, Xiantao
2010-03-15 14:18               ` Bastian Blank
2010-03-15 14:38                 ` Zhang, Xiantao
2010-03-15 21:15               ` Bastian Blank
2010-03-16  1:31                 ` Konrad Rzeszutek Wilk
2010-03-16  8:18                   ` Bastian Blank
2010-03-16 15:32                     ` Konrad Rzeszutek Wilk
2010-03-16 18:20                       ` Bastian Blank
2010-03-17  2:05                         ` Konrad Rzeszutek Wilk
2010-03-19 11:39                         ` Bastian Blank
2010-03-19 12:13                           ` Bastian Blank
2010-03-21 21:47                             ` Bastian Blank
2010-03-22  6:24                               ` Jeremy Fitzhardinge
2010-03-23 11:37                               ` Jan Beulich
2010-03-23 12:37                                 ` Bastian Blank
2010-03-23 14:04                                   ` Jan Beulich
2010-03-23 15:49                                     ` Bastian Blank
2010-03-19 14:15                           ` Zhang, Xiantao
2010-03-19 14:36                             ` Bastian Blank
2010-03-19  2:55                     ` Zhang, Xiantao
2010-03-19 11:06                       ` Bastian Blank [this message]
2010-03-14 16:41       ` Bastian Blank

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=20100319110613.GA29006@wavehammer.waldi.eu.org \
    --to=waldi@debian.org \
    --cc=jeremy@goop.org \
    --cc=keir.fraser@eu.citrix.com \
    --cc=konrad.wilk@oracle.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.