linux-kernel - Re: [kvm-devel] [RFC] Deferred interrupt handling.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <469F2D8C.7020805@qumranet.com>
Date:	Thu, 19 Jul 2007 12:23:24 +0300
From:	Avi Kivity <avi@...ranet.com>
To:	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Dor Laor <dor.laor@...ranet.com>,
	kvm-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [kvm-devel] [RFC] Deferred interrupt handling.

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/