From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: CONFIG_SPARSE_IRQ breaks single VCPU domain 0 between xen/master and xen/next
Date: Fri, 19 Mar 2010 16:45:30 -0700 [thread overview]
Message-ID: <4BA40C9A.3010902@goop.org> (raw)
In-Reply-To: <1269011246.10129.45553.camel@zakaz.uk.xensource.com>
On 03/19/2010 08:07 AM, Ian Campbell wrote:
> It looks like you guys have got the issue of identify the correct number
> of physical interrupts and handling the APIC setup correctly etc in hand
> but do we also need to consider taking the patch in
> http://lists.xensource.com/archives/html/xen-devel/2010-03/msg00028.html
> as well in order to ensure we have plenty of dynamic interrupts until
> such a time as they can be fully dynamically allocated?
>
Just reminded myself of this by booting a UP nested Xen. Pulled.
J
next prev parent reply other threads:[~2010-03-19 23:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 11:42 CONFIG_SPARSE_IRQ breaks single VCPU domain 0 between xen/master and xen/next Ian Campbell
2010-02-26 12:05 ` Ian Campbell
2010-02-26 16:17 ` Ian Campbell
2010-02-26 17:28 ` Jeremy Fitzhardinge
2010-03-01 9:41 ` Ian Campbell
2010-03-01 11:27 ` Ian Campbell
2010-03-19 18:11 ` Thomas Schwinge
2010-03-01 12:34 ` Zhang, Xiantao
2010-03-03 22:35 ` Jeremy Fitzhardinge
2010-03-05 2:41 ` Zhang, Xiantao
2010-03-19 15:07 ` Ian Campbell
2010-03-19 23:45 ` Jeremy Fitzhardinge [this message]
2010-02-28 12:01 ` Erik Brakkee
2010-02-28 20:12 ` Erik Brakkee
2010-03-01 10:33 ` Ian Campbell
2010-03-01 17:44 ` Erik Brakkee
2010-03-01 17:47 ` Konrad Rzeszutek Wilk
2010-03-01 19:36 ` Ian Campbell
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=4BA40C9A.3010902@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@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.