From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH] Make the hypercall PHYSDEVOP_alloc_irq_vector hypercall dummy.
Date: Thu, 03 Sep 2009 13:59:57 -0700 [thread overview]
Message-ID: <4AA02E4D.9080005@goop.org> (raw)
In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC201C43C4FB1@pdsmsx503.ccr.corp.intel.com>
On 09/03/09 06:14, Zhang, Xiantao wrote:
> IMO, dom0 should only cares about pirq(==GSI) and doesn't need to know the ifno about vector and specific apic&pin at all. Since Xen also knows GSI info, so dom0 and Xen can build irq mapping(xen's irq and dom0's pirq) through it.
Yes, but if dom0 rebinds the pirq<->gsi association, will Xen maintain
its internal structures correctly?
> Maybe we can get rid of ioapic in dom0 eventually.
>
Yes, I think so (see other mail).
J
prev parent reply other threads:[~2009-09-03 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 2:03 [PATCH] Make the hypercall PHYSDEVOP_alloc_irq_vector hypercall dummy Zhang, Xiantao
2009-09-02 21:46 ` Jeremy Fitzhardinge
2009-09-03 13:14 ` Zhang, Xiantao
2009-09-03 20:59 ` Jeremy Fitzhardinge [this message]
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=4AA02E4D.9080005@goop.org \
--to=jeremy@goop.org \
--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.