All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Alex Nixon <alex.nixon@citrix.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	the arch/x86 maintainers <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] Xen: Fix memory access violation bug when CONFIG_HAVE_SPARSE_IRQ is enabled
Date: Mon, 18 Aug 2008 14:39:19 -0700	[thread overview]
Message-ID: <48A9EC07.8000707@goop.org> (raw)
In-Reply-To: <48A976F7.8060808@citrix.com>

Alex Nixon wrote:
> From: Alex Nixon <alex.nixon@citrix.com>
> Date: Mon, 18 Aug 2008 14:15:11 +0100
> Subject: [PATCH] Xen: Fix memory access violation bug when CONFIG_HAVE_SPARSE_IRQ is enabled
>
> When sparse IRQs are enabled, it is not safe to assume an IRQ descriptor exists for every possible IRQ.  This patch causes init_evtchn_cpu_bindings to skip initialisation of IRQ descriptors which don't exist.
>
> Signed-off-by: Alex Nixon <alex.nixon@citrix.com>
>   

Thanks again, Alex.

Ingo, please apply.

Acked-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>

> ---
>  drivers/xen/events.c |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/xen/events.c b/drivers/xen/events.c
> index 74dca12..6e7e765 100644
> --- a/drivers/xen/events.c
> +++ b/drivers/xen/events.c
> @@ -141,6 +141,8 @@ static void init_evtchn_cpu_bindings(void)
>  	/* By default all event channels notify CPU#0. */
>  	for (i = 0; i < nr_irqs; i++) {
>  		struct irq_desc *desc = to_irq_desc(i);
> +		if (!desc)
> +			continue;
>  		desc->affinity = cpumask_of_cpu(0);
>  	}
>  #endif
>   


           reply	other threads:[~2008-08-18 21:39 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <48A976F7.8060808@citrix.com>]

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=48A9EC07.8000707@goop.org \
    --to=jeremy@goop.org \
    --cc=alex.nixon@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=x86@kernel.org \
    /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.