Subject: Re: ioapic: adaption required?
To: Christoph Egger <Christoph_Egger@gmx.de>
From: Manuel Bouyer <email@example.com>
Date: 10/08/2007 13:33:38
On Mon, Oct 08, 2007 at 01:22:32PM +0200, Christoph Egger wrote:
> > xen/include/i82093var.h Or maybe you mean to use APIC operations to
> > query/ack the interrupts instead of these hypercalls ?
> I'm talking about the hypercall used in pirq_establish() in xen/evtchn.c.
Do you know what should be used instead now ?
> > Anyway, it looks like the new ACPI code makes changes to the configuration
> > that Xen considers bogus or invalid; or maybe just changing routing for
> > interrupts that already have an handler installed. I'm not sure getting rid
> > of PHYSDEVOP_IRQ_* would fix it ...
> oh, there is a difference:
> The deprecated PHYSDEVOP_IRQ_* hypercalls only update the evtchn_*
> members in the shared_info page.
> With PHYSDEVOP_apic_read and PHYSDEVOP_apic_write, Xen truely
> talks to the ioapic.
Sure. But we're already using the PHYSDEVOP_apic_read/write hypercalls to
talk to the ioapic.
Manuel Bouyer, LIP6, Universite Paris VI. Manuel.Bouyer@lip6.fr
NetBSD: 26 ans d'experience feront toujours la difference