From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: linux-kernel@vger.kernel.org,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
xen-devel@lists.xensource.com,
Konrad Rzeszutek Wilk <konrad@kernel.org>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH] Fix when booting Xen+Linux under QEMU.
Date: Thu, 9 Dec 2010 22:55:00 -0500 [thread overview]
Message-ID: <20101210035500.GA17525@dumpdata.com> (raw)
In-Reply-To: <4D01462A.4010808@goop.org>
> I think I'd prefer to:
>
> 1. move to using all dynamic irqs, and use the core kernel irq
> allocator (ie, resurrect IanC's patches)
That would make it easier, except that they don't work when you have DomU
guest with Xen PCI front. Simply b/c the DomU guest has no idea of what GSI of
the host machine is. Hence the find_unbound_irq that starts from the top
(nr_irqs) and goes down to GSI count (nr_irq_gsi).
Maybe we can stick it in the Xen PCIfronted/Xen PCI backend a mechanism (some
key value) which will specify the host's nr_irq_gsi value. Then the DomU guest
can set that and then use the core kernel irq allocator...
next prev parent reply other threads:[~2010-12-10 3:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 21:01 [PATCH] Fix when booting Xen+Linux under QEMU Konrad Rzeszutek Wilk
2010-12-09 21:01 ` [PATCH 1/2] xen/irq: Cleanup the find_unbound_irq Konrad Rzeszutek Wilk
2010-12-09 21:01 ` [PATCH 2/2] xen/irq: Don't fall over when nr_irqs_gsi > nr_irqs Konrad Rzeszutek Wilk
2010-12-09 21:12 ` [PATCH] Fix when booting Xen+Linux under QEMU Jeremy Fitzhardinge
2010-12-09 21:12 ` Jeremy Fitzhardinge
2010-12-10 3:55 ` Konrad Rzeszutek Wilk [this message]
2010-12-10 13:02 ` Stefano Stabellini
2010-12-10 13:02 ` Stefano Stabellini
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=20101210035500.GA17525@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=jeremy@goop.org \
--cc=konrad@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.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.