From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] Move irq sharing information to irqchip level.
Date: Sun, 23 Aug 2009 14:56:58 +0300 [thread overview]
Message-ID: <20090823115658.GB30093@redhat.com> (raw)
In-Reply-To: <4A912C1E.5090004@redhat.com>
On Sun, Aug 23, 2009 at 02:46:38PM +0300, Avi Kivity wrote:
> On 08/23/2009 02:36 PM, Gleb Natapov wrote:
> >>>
> >>>The problem is that at this level it is not known if GSI is MSI or not.
> >>>Current code dials with this by arbitrary assuming that GSI is MSI if it
> >>>is greater then KVM_IOAPIC_NUM_PINS, but this is not enforced when
> >>>routing table is installed and userspace is free to use any GSI as MSI.
> >>>Of cause this problem would not exist if MSIs were not linked to GSIs
> >>>in the first place.
> >>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?
> >>No, it's more correct at the GSI level, since all interrupt lines
> >>connected to one GSI are shared.
> >>
> >Why? All interrupts connected to the same irqchip pin (through pci irq
> >router or other onboard logic) are shared. GSI is pure logical
> >abstraction.
>
> 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?
--
Gleb.
next prev parent reply other threads:[~2009-08-23 11:56 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 [this message]
2009-08-23 12:02 ` 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=20090823115658.GB30093@redhat.com \
--to=gleb@redhat.com \
--cc=avi@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).