From: Sasha Levin <levinsasha928@gmail.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: mingo@elte.hu, asias.hejun@gmail.com, gorcunov@gmail.com,
prasadjoshi124@gmail.com, kvm@vger.kernel.org
Subject: Re: [PATCH 1/2] kvm tools: Fix IRQ assignments
Date: Fri, 06 May 2011 11:01:16 +0300 [thread overview]
Message-ID: <1304668876.10534.9.camel@lappy> (raw)
In-Reply-To: <BANLkTinhY8zSoSCyKcTSVVuTtN69DMn_Tw@mail.gmail.com>
On Fri, 2011-05-06 at 10:43 +0300, Pekka Enberg wrote:
> On Fri, May 6, 2011 at 10:36 AM, Sasha Levin <levinsasha928@gmail.com> wrote:
> > afaik, we need to have same IRQ pins for devices which may have
> > different IRQ lines (All virtio-blk share same IRQ pin but different
> > line, I assume it'll be same with different virtio devices).
> >
> > So mptable has to manage association between device type and the
> > corresponding IRQ pin/line assignment, So dynamic assignment will be
> > more of a call with device type and return IRQ pin + line - which makes
> > it more complex than just allocating next free IRQ line.
>
> Well then make kvm__request_irq() return a pointer to struct irq and
> have a hard-coded array of IRQ pin + line pairs in irq.c, for example.
> That'll reduce complexity in the virtio drivers and it'll serve as a
> starting point for proper IRQ allocator.
The big problem with dynamic allocations is having mptable register IRQ
sources properly, So I went ahead and deleted IRQ source definitions
from mptable.c and noticed that everything still works.
I've spoke with Cyrill and neither him or myself were too sure if it's
ok to do that now and if so, would it still be correct once SMP gets
added.
So here is my question: Would it be ok to drop IRQ source definitions
from mptable?
--
Sasha.
next prev parent reply other threads:[~2011-05-06 8:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 7:26 [PATCH 1/2] kvm tools: Fix IRQ assignments Sasha Levin
2011-05-06 7:26 ` [PATCH 2/2] kvm tools: Simplify search for root device Sasha Levin
2011-05-07 8:41 ` Pekka Enberg
2011-05-07 8:46 ` Sasha Levin
2011-05-07 8:49 ` Prasad Joshi
2011-05-06 7:29 ` [PATCH 1/2] kvm tools: Fix IRQ assignments Pekka Enberg
2011-05-06 7:31 ` Cyrill Gorcunov
2011-05-06 7:36 ` Sasha Levin
2011-05-06 7:43 ` Pekka Enberg
2011-05-06 8:01 ` Sasha Levin [this message]
2011-05-06 8:04 ` Pekka Enberg
2011-05-06 8:08 ` Cyrill Gorcunov
2011-05-06 8:10 ` Pekka Enberg
2011-05-06 8:16 ` Cyrill Gorcunov
2011-05-06 7:47 ` Cyrill Gorcunov
2011-05-06 7:59 ` Pekka Enberg
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=1304668876.10534.9.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=prasadjoshi124@gmail.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