All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: "Tian, Kevin" <kevin.tian@intel.com>, Doi.Tsunehisa@jp.fujitsu.com
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Alex Williamson <alex.williamson@hp.com>
Subject: Re: [PATCH] Change spec of callback IRQ forPV-on-HVMonIA64
Date: Tue, 21 Nov 2006 11:33:10 +0000	[thread overview]
Message-ID: <C1889476.4D01%keir@xensource.com> (raw)
In-Reply-To: <D470B4E54465E3469E2ABBC5AFAC390F051404@pdsmsx412.ccr.corp.intel.com>

On 21/11/06 10:56, "Tian, Kevin" <kevin.tian@intel.com> wrote:

>> OK, I now understand. Other OS tells xen GSI number as callback_irq,
>> and then xen look up virtual interrupt controller to find appropriate
>> vector by GSI number. This is the way to go. :-)
>> 
>> Thanks a lot,
>> Kevin
>> 
> 
> Keir mentioned in another thread that he will change qemu to support
> more GSIs (>16) soon, and this will become an issue with your patch
> since you're only looking at isa_irq_to_vector. Is there any common
> approach exported by linux kernel to find vector->GSI mapping in
> driver? If not, maybe an alternative is to provide a callback_irq_type
> which indicates whether the value is a GSI or vector?

We plan to add a callback_vector type to the Xen interface for x86 HVM, as
we will deliver event-channel notifications via an MSI-style poke directly
into the IRR of the appropriate local APIC. We'll continue to support
callback_irq type for compatibility.

 -- Keir

  parent reply	other threads:[~2006-11-21 11:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21 10:56 [PATCH] Change spec of callback IRQ forPV-on-HVMonIA64 Tian, Kevin
2006-11-21 11:12 ` Doi.Tsunehisa
2006-11-21 11:33 ` Keir Fraser [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-21 11:37 Tian, Kevin

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=C1889476.4D01%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=Doi.Tsunehisa@jp.fujitsu.com \
    --cc=alex.williamson@hp.com \
    --cc=kevin.tian@intel.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.