All of lore.kernel.org
 help / color / mirror / Atom feed
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 12:23:24 +0300	[thread overview]
Message-ID: <469F2D8C.7020805@qumranet.com> (raw)
In-Reply-To: <20070718191433.GB24545@csclub.uwaterloo.ca>

Lennart Sorensen wrote:
> On Wed, Jul 18, 2007 at 07:46:13PM +0300, Avi Kivity wrote:
>   
>> IMO the only reasonable solution is to disallow interrupt forwarding
>> with shared irqs.  If someone later comes up with a bright idea, we can
>> implement it.  Otherwise the problem will solve itself with hardware
>> moving to msi.
>>     
>
> Disallowing shared IRQs means disallowing PCI devices in general, so now
> you are back to ISA only devices, which it sounds like were the only
> things already allowed by vm86 or whatever it was for passing through.
>
>   

No, it means disallowing pci devices that use shared irqs, and allowing 
pci devices that use non-shared irqs.

> Certainly does appear to have potential though for allowing more
> interesting virtual machines.
>   

IMO pass-through is counter to most of the benefits of virtualization.  
But users seem to want it.

-- 
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 12:23:24 +0300	[thread overview]
Message-ID: <469F2D8C.7020805@qumranet.com> (raw)
In-Reply-To: <20070718191433.GB24545-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys@public.gmane.org>

Lennart Sorensen wrote:
> On Wed, Jul 18, 2007 at 07:46:13PM +0300, Avi Kivity wrote:
>   
>> IMO the only reasonable solution is to disallow interrupt forwarding
>> with shared irqs.  If someone later comes up with a bright idea, we can
>> implement it.  Otherwise the problem will solve itself with hardware
>> moving to msi.
>>     
>
> Disallowing shared IRQs means disallowing PCI devices in general, so now
> you are back to ISA only devices, which it sounds like were the only
> things already allowed by vm86 or whatever it was for passing through.
>
>   

No, it means disallowing pci devices that use shared irqs, and allowing 
pci devices that use non-shared irqs.

> Certainly does appear to have potential though for allowing more
> interesting virtual machines.
>   

IMO pass-through is counter to most of the benefits of virtualization.  
But users seem to want it.

-- 
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/

  reply	other threads:[~2007-07-19  9:23 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           ` Avi Kivity [this message]
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               ` [kvm-devel] " Avi Kivity
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=469F2D8C.7020805@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.