public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: No disable_irq for MSI/MSI-X interrupt on device assignment
Date: Mon, 04 May 2009 11:25:55 +0300	[thread overview]
Message-ID: <49FEA693.8020303@redhat.com> (raw)
In-Reply-To: <1241060322-25807-1-git-send-email-sheng@linux.intel.com>

Sheng Yang wrote:
> Disable interrupt at interrupt handler and enable it when guest ack is for
> the level triggered interrupt, to prevent reinjected interrupt. MSI/MSI-X don't
> need it.
>
> One possible problem is multiply same vector interrupt injected between irq
> handler and scheduled work handler would be merged as one for MSI/MSI-X.
> But AFAIK, the drivers handle it well.
>
> The patch fixed the oplin card performance issue(MSI-X performance is half of
> MSI/INTx).
>
>  
>  	schedule_work(&assigned_dev->interrupt_work);
>  
> -	disable_irq_nosync(irq);
> -	assigned_dev->host_irq_disabled = true;
> +	if (assigned_dev->irq_requested_type & KVM_DEV_IRQ_GUEST_INTX) {
> +		disable_irq_nosync(irq);
> +		assigned_dev->host_irq_disabled = true;
> +	}
>  
>  out:
>  	spin_unlock_irqrestore(&assigned_dev->assigned_dev_lock, flags);
>   

I don't have the spin_lock_irqrestore() here.  The patch applies, but 
with fuzz.  Am I missing a patch?

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  reply	other threads:[~2009-05-04  8:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30  2:58 [PATCH] KVM: No disable_irq for MSI/MSI-X interrupt on device assignment Sheng Yang
2009-05-04  8:25 ` Avi Kivity [this message]
2009-05-04  8:30   ` Sheng Yang
2009-05-04  8:34     ` Avi Kivity
2009-05-04  8:37       ` Sheng Yang
2009-05-31  9:48 ` Avi Kivity

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=49FEA693.8020303@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=sheng@linux.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