xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@schwinge.name>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: waldi@debian.org, Jeremy Fitzhardinge <jeremy@goop.org>,
	xen-devel@lists.xensource.com, 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 19:11:50 +0100	[thread overview]
Message-ID: <20100319181150.GA5645@dirichlet.schwinge.homeip.net> (raw)
In-Reply-To: <1267442837.11737.20729.camel@zakaz.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 1243 bytes --]

Hello!

Ian, thanks for pointing me to this patch:

On Mon, Mar 01, 2010 at 11:27:17AM +0000, Ian Campbell wrote:
> >From 6d4a9168207ade237098a401270959ecc0bdd1e9 Mon Sep 17 00:00:00 2001
> From: Ian Campbell <ian.campbell@citrix.com>
> Date: Mon, 1 Mar 2010 11:21:15 +0000
> Subject: [PATCH] xen: allow some overhead in IRQ space for dynamic IRQs
>  such as VIRQs and backend event channels.
> 
> This is an interim solution until x86 interrupts become totally dynamic.
> 
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> ---
>  arch/x86/include/asm/irq_vectors.h |   14 +++++++++++---
>  arch/x86/kernel/apic/io_apic.c     |    4 ++++
>  arch/x86/xen/enlighten.c           |    4 ++++
>  3 files changed, 19 insertions(+), 3 deletions(-)

This patch fixes the issue (``No available IRQ to bind to: increase
nr_irqs!'') that I reported in
<http://lists.debian.org/debian-kernel/2010/03/msg00665.html>, thus feel
free to add ``Tested-by: Thomas Schwinge <thomas@schwinge.name>''.

I put this one commit on top of whatever Debian's
linux-image-2.6.32-4-xen-amd64 2.6.32-10 package has, and am now running
that one on my AMD Sempron system: uni-processor, no hardware
virtualization.


Regards,
 Thomas

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-03-19 18:11 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 [this message]
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
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=20100319181150.GA5645@dirichlet.schwinge.homeip.net \
    --to=thomas@schwinge.name \
    --cc=Ian.Campbell@citrix.com \
    --cc=jeremy@goop.org \
    --cc=waldi@debian.org \
    --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).