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 for Android: free password hash cracker in your pocket

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

Message-ID: <20070718224649.3e49a978@the-village.bc.nu>
Date:	Wed, 18 Jul 2007 22:46:49 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Dor Laor" <dor.laor@...ranet.com>
Cc:	"Avi Kivity" <avik@...ranet.com>,
	<kvm-devel@...ts.sourceforge.net>, <linux-kernel@...r.kernel.org>
Subject: Re: [kvm-devel] [RFC] Deferred interrupt handling.

> - Make the device the last irqaction in the list
> - Our dummy handler will always return IRQ_HANDLED in case any other
> previous
>   irqaction did not return such. It will also issue the timer and mask
> the irq in this case.

Ok

>   btw, if I'm not mistaken only after bad 99900/100000 the irq is
> disabled.

(and with GIT providing that they occurred in a short time period)

> - If the timer pops before the guest acks the irq, the timer handler
> will
>   ack the irq and unmask it. The timer's job is only to prevent
> deadlocks.

Ok I see what you are doing. It's either inspired or insane and I am not
quite sure which of the two. I agree it should work although may cause
performance crunches now and then and will also need care getting the
locking right.

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