From: Avi Kivity <avi@qumranet.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Dor Laor <dor.laor@qumranet.com>,
kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [kvm-devel] [RFC] Deferred interrupt handling.
Date: Thu, 19 Jul 2007 16:38:09 +0300 [thread overview]
Message-ID: <469F6941.9010901@qumranet.com> (raw)
In-Reply-To: <20070719131718.GC5623@csclub.uwaterloo.ca>
Lennart Sorensen wrote:
> On Thu, Jul 19, 2007 at 12:23:24PM +0300, Avi Kivity wrote:
>
>> No, it means disallowing pci devices that use shared irqs, and allowing
>> pci devices that use non-shared irqs.
>>
>
> Most machiens I see today have almost no chance of having PCI devices
> without shared IRQs. This probably means any implementation will only
> work on a small set of machines with very specific setup in terms of
> which PCI slots they install cards in, and only as long as you don't
> allow any type of hotplugging of devices (or ever changing hardware at
> all). May not be worth implementing if it has such a limited use case.
> The MSI setup on the other hand does sound like it might have potential
> for working in general.
>
>
Looking at two random servers here and a desktop, interrupts are
unshared except for usb. A laptop was not so lucky. So "no chance" is
a bit extreme.
I agree it's far from optimal, but it is less limited than you imply.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Lennart Sorensen
<lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC] Deferred interrupt handling.
Date: Thu, 19 Jul 2007 16:38:09 +0300 [thread overview]
Message-ID: <469F6941.9010901@qumranet.com> (raw)
In-Reply-To: <20070719131718.GC5623-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys@public.gmane.org>
Lennart Sorensen wrote:
> On Thu, Jul 19, 2007 at 12:23:24PM +0300, Avi Kivity wrote:
>
>> No, it means disallowing pci devices that use shared irqs, and allowing
>> pci devices that use non-shared irqs.
>>
>
> Most machiens I see today have almost no chance of having PCI devices
> without shared IRQs. This probably means any implementation will only
> work on a small set of machines with very specific setup in terms of
> which PCI slots they install cards in, and only as long as you don't
> allow any type of hotplugging of devices (or ever changing hardware at
> all). May not be worth implementing if it has such a limited use case.
> The MSI setup on the other hand does sound like it might have potential
> for working in general.
>
>
Looking at two random servers here and a desktop, interrupts are
unshared except for usb. A laptop was not so lucky. So "no chance" is
a bit extreme.
I agree it's far from optimal, but it is less limited than you imply.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-07-19 13:38 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 9:53 [RFC] Deferred interrupt handling Or Sagi
2007-07-18 9:53 ` Or Sagi
2007-07-18 11:30 ` Alan Cox
2007-07-18 11:30 ` Alan Cox
2007-07-18 16:36 ` [kvm-devel] " Dor Laor
2007-07-18 16:36 ` Dor Laor
2007-07-18 16:47 ` [kvm-devel] " Alan Cox
2007-07-18 16:47 ` Alan Cox
2007-07-18 16:46 ` [kvm-devel] " Avi Kivity
2007-07-18 16:46 ` Avi Kivity
2007-07-18 16:57 ` [kvm-devel] " Alan Cox
2007-07-18 16:57 ` Alan Cox
2007-07-18 16:57 ` [kvm-devel] " Avi Kivity
2007-07-18 16:57 ` Avi Kivity
2007-07-18 17:14 ` [kvm-devel] " Alan Cox
2007-07-18 17:14 ` Alan Cox
2007-07-18 17:09 ` [kvm-devel] " Dor Laor
2007-07-18 17:09 ` Dor Laor
2007-07-18 17:33 ` [kvm-devel] " Alan Cox
2007-07-18 17:33 ` Alan Cox
2007-07-18 21:29 ` [kvm-devel] " Dor Laor
2007-07-18 21:29 ` Dor Laor
2007-07-18 21:46 ` [kvm-devel] " Alan Cox
2007-07-18 21:46 ` Alan Cox
2007-07-25 14:18 ` [kvm-devel] " Pavel Machek
2007-07-25 14:18 ` Pavel Machek
2007-07-18 22:23 ` [kvm-devel] " Or Sagi
2007-07-18 22:23 ` Or Sagi
2007-07-18 19:14 ` [kvm-devel] " Lennart Sorensen
2007-07-18 19:14 ` Lennart Sorensen
2007-07-19 9:23 ` [kvm-devel] " Avi Kivity
2007-07-19 9:23 ` Avi Kivity
2007-07-19 13:17 ` [kvm-devel] " Lennart Sorensen
2007-07-19 13:17 ` Lennart Sorensen
2007-07-19 13:38 ` Avi Kivity [this message]
2007-07-19 13:38 ` Avi Kivity
2007-07-19 16:23 ` [kvm-devel] " Lennart Sorensen
2007-07-19 16:23 ` Lennart Sorensen
2007-07-18 15:57 ` Lennart Sorensen
2007-07-18 15:57 ` Lennart Sorensen
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=469F6941.9010901@qumranet.com \
--to=avi@qumranet.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dor.laor@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.