[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 1/1] Introduce a new bus "ICC" to connect APIC
From: |
Jan Kiszka |
Subject: |
Re: [Qemu-devel] [PATCH 1/1] Introduce a new bus "ICC" to connect APIC |
Date: |
Sun, 23 Oct 2011 17:45:42 +0200 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 |
On 2011-10-23 14:40, Blue Swirl wrote:
> I'm not sure that a full bus is needed for now, even if it could match
> real HW better, since the memory API already provides the separation
> needed. Perhaps this would be needed later to make IRQs per-CPU also,
> or to put IOAPIC also to the bus?
The ICC interconnects LAPICs and IOAPICs. So it should next take over
the management of the local_apics array from apic.c and the ioapics
array from ioapic.c. It could implement generic message delivery
services. Every bus participant would then have a reception handler that
first checks the type and additional fields of a generic ICC message
and, on match, forwards it to the corresponding device model functions.
That would allow for something nicer than global apic_deliver_irq or
ioapic_eoi_broadcast.
That's clearly beyond the scope of this series but a good reason to
model the ICC as accurately as qdev allows right from the start.
Jan
signature.asc
Description: OpenPGP digital signature
Re: [Qemu-devel] [PATCH 1/1] Introduce a new bus "ICC" to connect APIC, Blue Swirl, 2011/10/23
- Re: [Qemu-devel] [PATCH 1/1] Introduce a new bus "ICC" to connect APIC,
Jan Kiszka <=
Re: [Qemu-devel] [PATCH 1/1] Introduce a new bus "ICC" to connect APIC, liu ping fan, 2011/10/25