On Tue, Nov 04, 2008 at 01:57:56PM +0200, Avi Kivity wrote:
> Sheng Yang wrote:
>> Yes, in theory, we got a little trouble, but not that much.
>>
>> The mechanism based on a assumption: every time guest got a interrupt,
>> it would deassert the interrupt source sooner or later. So we take the
>>
Sheng Yang wrote:
Yes, in theory, we got a little trouble, but not that much.
The mechanism based on a assumption: every time guest got a interrupt, it
would deassert the interrupt source sooner or later. So we take the Ack action
as the same as deassert the IRQ line here (unmasked the IRQ).
On Tuesday 04 November 2008 19:25:34 Avi Kivity wrote:
> Sheng Yang wrote:
> > Now we use MSI as default one, and translate MSI to INTx when guest need
> > INTx rather than MSI. For legacy device, we provide support for
> > non-sharing host IRQ.
>
> Won't we run into trouble with edge-triggered vs
Sheng Yang wrote:
Now we use MSI as default one, and translate MSI to INTx when guest need INTx
rather than MSI. For legacy device, we provide support for non-sharing host
IRQ.
Won't we run into trouble with edge-triggered vs level-triggered.
--
error compiling committee.c: too many argume
Now we use MSI as default one, and translate MSI to INTx when guest need INTx
rather than MSI. For legacy device, we provide support for non-sharing host
IRQ.
Signed-off-by: Sheng Yang <[EMAIL PROTECTED]>
---
virt/kvm/kvm_main.c | 52 --
1 files c
Now we use MSI as default one
Signed-off-by: Sheng Yang <[EMAIL PROTECTED]>
---
virt/kvm/kvm_main.c | 50 +++---
1 files changed, 27 insertions(+), 23 deletions(-)
diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
index 0f851ef..34b5d2f 100644
-
