From: Avi Kivity <avi@redhat.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Gleb Natapov <gleb@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH 0/5 v9] Optimize and unify IOAPIC/MSI delivery
Date: Wed, 25 Feb 2009 12:44:41 +0200 [thread overview]
Message-ID: <49A52119.4020405@redhat.com> (raw)
In-Reply-To: <49A51E3A.1000309@redhat.com>
>> Rebased on latest upstream. The changes are "Report IRQ injection
>> status"
>> related in the second patch.
>>
>> The v8 was acked by Marcelo Tosatti.
>>
>
> I just merged this (and resolved all the conflicts...). I'll see if
> there are any changes between the two sets.
>
Gleb tells me that my version is better wrt irq injection status
reporting, so I'll keep it.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-02-25 10:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 9:18 [PATCH 0/5 v9] Optimize and unify IOAPIC/MSI delivery Sheng Yang
2009-02-25 9:18 ` [PATCH 1/5] KVM: Split IOAPIC structure Sheng Yang
2009-02-25 9:18 ` [PATCH 2/5] KVM: Unified the delivery of IOAPIC and MSI Sheng Yang
2009-02-25 9:18 ` [PATCH 3/5] KVM: Change API of kvm_ioapic_get_delivery_bitmask Sheng Yang
2009-02-25 9:18 ` [PATCH 4/5] KVM: Update intr delivery func to accept unsigned long* bitmap Sheng Yang
2009-02-25 9:18 ` [PATCH 5/5] KVM: bit ops for deliver_bitmap Sheng Yang
2009-02-25 10:32 ` [PATCH 0/5 v9] Optimize and unify IOAPIC/MSI delivery Avi Kivity
2009-02-25 10:44 ` Avi Kivity [this message]
2009-02-26 1:53 ` Sheng Yang
2009-02-26 12:39 ` [PATCH] kvm: declare kvm_ioapic in kvm_host.h Christian Borntraeger
2009-02-26 12:43 ` Avi Kivity
2009-02-26 12:55 ` Christian Borntraeger
2009-02-26 13:01 ` Avi Kivity
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=49A52119.4020405@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=sheng@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox