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

Re: [Xen-devel] x86: clear_IO_APIC_pin() and SMI delivery mode

  • To: Jan Beulich <jbeulich@xxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Wed, 06 Feb 2008 14:01:04 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 06 Feb 2008 06:01:53 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AchoyLY59QTOKNS7Edy8iQAX8io7RQ==
  • Thread-topic: [Xen-devel] x86: clear_IO_APIC_pin() and SMI delivery mode

On 6/2/08 13:55, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

>> That's what we've done since Xen 3.1.1. See xen-unstable c/s 15270 (15184 in
>> 3.1-testing).
> Hmm, I admit I again failed to look at the -unstable code, but isn't the
> WARN_BOGUS_WRITE() itself a little bogus, especially if the entry is
> masked?

It's nice to know if we take that path. Actually most dom0 boots will get
one or two WARN_BOGUS_WRITE() outputs (modifying IO-APIC pin for in-use
IRQ), of course they're almost always benign, and hence it's rather up to
you if you want to quieten that down for use in your product. But the
messages aren't too scary-looking, I think.

 -- Keir

Xen-devel mailing list



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