mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86, irq: Check if irq is remapped before freeing irte
Date: Mon, 18 Oct 2010 23:09:23 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1010182304050.6815@localhost6.localdomain6> (raw)
In-Reply-To: <4CBCB274.7010108@kernel.org>

On Mon, 18 Oct 2010, Yinghai Lu wrote:
> 
> Index: linux-2.6/drivers/pci/intr_remapping.c
> ===================================================================
> --- linux-2.6.orig/drivers/pci/intr_remapping.c
> +++ linux-2.6/drivers/pci/intr_remapping.c
> @@ -60,7 +60,7 @@ int get_irte(int irq, struct irte *entry
>  	unsigned long flags;
>  	int index;
>  
> -	if (!entry || !irq_iommu)
> +	if (!entry || !irq_iommu || !irq_iommu->iommu)
>  		return -1;

Hmm, why do we need this? This is only called from
ir_ioapic_set_affinity() and ir_msi_set_affinity().

We should never end up there when intr_remapping=off, right ?
  
>  	spin_lock_irqsave(&irq_2_ir_lock, flags);
> @@ -268,7 +268,7 @@ int free_irte(int irq)
>  	unsigned long flags;
>  	int rc;
>  
> -	if (!irq_iommu)
> +	if (!irq_iommu || !irq_iommu->iommu)
>  		return -1;

That one makes sense

Thanks,

	tglx

  reply	other threads:[~2010-10-18 21:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-18 20:47 Yinghai Lu
2010-10-18 21:09 ` Thomas Gleixner [this message]
2010-10-18 21:17   ` Thomas Gleixner
2010-10-18 21:28     ` Yinghai
2010-10-18 22:22     ` Yinghai Lu
2010-10-18 22:31       ` Thomas Gleixner
2010-10-18 22:47         ` Yinghai Lu
2010-10-19  7:28 ` [tip:irq/core] x86: ioapic: Call free_irte only if interrupt remapping enabled tip-bot for Yinghai Lu

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=alpine.LFD.2.00.1010182304050.6815@localhost6.localdomain6 \
    --to=tglx@linutronix.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®