|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] Re: [GIT PULL] Xen APIC hooks (with io_apic_ops)
* Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> Hi Ingo,
>
> Here's a revised set of the Xen APIC changes which adds
> io_apic_ops to allow Xen to intercept IO APIC access operations.
In a previous discussion you said:
> IO APIC operations are not even slightly performance critical? Are
> they ever used on the interrupt delivery path?
Since they are not performance critical, then why doesnt Xen catch
the IO-APIC accesses, and virtualizes the device?
If you want to hook into the IO-APIC code at such a low level, why
dont you hook into the _hardware_ API - i.e. catch those
setup/routing modifications to the IO-APIC space. No Linux changes
are needed in that case.
Ingo
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] [PATCH 09/17] xen: bind pirq to vector and event channel, (continued)
- [Xen-devel] [PATCH 09/17] xen: bind pirq to vector and event channel, Jeremy Fitzhardinge
- [Xen-devel] [PATCH 08/17] xen: direct irq registration to pirq event channels, Jeremy Fitzhardinge
- [Xen-devel] [PATCH 05/17] xen: implement pirq type event channels, Jeremy Fitzhardinge
- [Xen-devel] [PATCH 11/17] xen: don't setup acpi interrupt unless there is one, Jeremy Fitzhardinge
- [Xen-devel] [PATCH 13/17] xen: initialize irq 0 too, Jeremy Fitzhardinge
- [Xen-devel] [PATCH 10/17] xen: pre-initialize legacy irqs early, Jeremy Fitzhardinge
- [Xen-devel] [PATCH 14/17] xen: dynamically allocate irq & event structures, Jeremy Fitzhardinge
- [Xen-devel] [PATCH 15/17] xen: set pirq name to something useful., Jeremy Fitzhardinge
- [Xen-devel] [PATCH 16/17] xen: fix legacy irq setup, make ioapic-less machines work., Jeremy Fitzhardinge
- [Xen-devel] [PATCH 17/17] xen: disable MSI, Jeremy Fitzhardinge
- [Xen-devel] Re: [GIT PULL] Xen APIC hooks (with io_apic_ops),
Ingo Molnar <=
|
|
|
|
|