kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] Move irq sharing information to irqchip level.
Date: Sun, 23 Aug 2009 15:02:18 +0300	[thread overview]
Message-ID: <4A912FCA.4060800@redhat.com> (raw)
In-Reply-To: <20090823115658.GB30093@redhat.com>

On 08/23/2009 02:56 PM, Gleb Natapov wrote:
>>>> Does msi actually care about the states?  I don't think it does.
>>>>          
>>> That is the point. MSI doesn't care, but we don't know if GSI is MSI or
>>> not.
>>>        
>> So we toggle the bits needlessly.  Just like with edge-triggered interrupts.
>>      
> If we can avoid it why not?
>    

It simplifies the code.  You do it at the kvm_set_irq() entry point 
regardless of whether the interrupt is level-triggered, edge-triggered, 
or msi.  As a bonus, you only do it once (not twice for pic/ioapic 
interrupts).

>> All interrupts connected through one GSI are shared, so why not keep
>> the level information shared as well?
>>
>>      
> If we will keep sharing info at irq routing table level how will we recalculate
> sharing state when irq routing table changes?
>    

Good question.  Move from old table to new table? but that interferes 
with rcu.

Okay, at irqchip level is better after all.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2009-08-23 12:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 17:19 [PATCH] Move irq sharing information to irqchip level Gleb Natapov
2009-08-17  9:35 ` Avi Kivity
2009-08-21 18:16   ` Gleb Natapov
2009-08-23 11:28     ` Avi Kivity
2009-08-23 11:36       ` Gleb Natapov
2009-08-23 11:46         ` Avi Kivity
2009-08-23 11:56           ` Gleb Natapov
2009-08-23 12:02             ` Avi Kivity [this message]

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=4A912FCA.4060800@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.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;
as well as URLs for NNTP newsgroup(s).