[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] High CPU temp, suspend problem - xen 4.1.5-pre, linux 3.7.x

>>> On 28.03.13 at 13:54, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:
>>>> On 28.03.13 at 12:53, Andrew Cooper <andrew.cooper3@xxxxxxxxxx> wrote:
>> On 28/03/2013 10:50, Jan Beulich wrote:
>>> x86: irq_move_cleanup_interrupt() must ignore legacy vectors
>>> Since the main loop in the function includes legacy vectors, and since
>>> vector_irq[] gets set up for legacy vectors regardless of whether those
>>> get handled through the IO-APIC, it must not do anything on this vector
>>> range. In fact, we should never get here for IRQs not handled through
>>> the IO-APIC, so add a respective warning at once (could probably as
>>> well be an ASSERT()).
>>> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
>> Under what circumstances would we have any vectors 0xe0-0xef programmed
>> into the IOAPIC?  I cant think of any offhand.
> Never. And I didn't say it would.
>> As far as I am aware, it is not valid for any PIC interrupts to ever be
>> up for moving, as they should only be delivered to the BSP.
> Hence the WARN_ON() (or ASSERT()).

You know what - now that I actually tried this out, I see that this
triggers. For the moment I'm puzzled, will need to look into this in
more detail.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.