xen-devel.lists.xenproject.org archive mirror
 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>,
	Keir 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 15:36:01 +0100	[thread overview]
Message-ID: <20100319143601.GA875@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <EB8593BCECAB3D40A8248BE0B6400A384652033C@shzsmsx502.ccr.corp.intel.com>

On Fri, Mar 19, 2010 at 10:15:23PM +0800, Zhang, Xiantao wrote:
> Bastian Blank wrote:
> > I did some digging and found similar code that disallows
> > reprogramming of IO-APIC pins in
> > arch/x86/kernel/apic/io_apic.c:io_apic_set_pci_routing
> > So this behaviour is correct.
> > So the question is: Is it wrong for the kernel to do register_gsi
> > calls early in bootup for interrupts it does not know anything about?
> 
> I remembered you mentioned that you hacked hypervisor and allows
> re-programme for the special gsi and everying goes well. If you only
> hacked hypervisor in your case, and I think the hypervisor patch
> should be enough.

Only if we can distinguish between the two registrations, IMHO we can't.
So the kernel must not do them in the first case or we need to add
something to distiguish. IMHO the first solution is easier and should
work.

> Could you attach the full log ?

No, I have none. But there is nothing new in it over the last one
anyway.

Bastian

-- 
No one wants war.
		-- Kirk, "Errand of Mercy", stardate 3201.7

  reply	other threads:[~2010-03-19 14:36 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 [this message]
2010-03-19  2:55                     ` Zhang, Xiantao
2010-03-19 11:06                       ` Bastian Blank
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=20100319143601.GA875@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 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).