From: Jason Andryuk <jandryuk@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Aaron Janse <aaron@ajanse.me>, Jan Beulich <jbeulich@suse.com>
Subject: Re: [Xen-devel] [BUG] panic: "IO-APIC + timer doesn't work" - several people have reproduced
Date: Wed, 4 Mar 2020 11:05:22 -0500 [thread overview]
Message-ID: <CAKf6xpuRQDvHc6WjrSmaa-NO-++LGVU7Rf+prj0L0DzTjEPh+Q@mail.gmail.com> (raw)
In-Reply-To: <CAKf6xpt26=s_+cD63VJ1Cp3WZvtq3p673uUiqiuDHAVH=ZJOcQ@mail.gmail.com>
> > >>> One other thing that might be noteworthy. Linux only prints ACPI IRQ0
> > >>> and IRQ9 used by override where Xen lists IRQ 0, 2 & 9.
> > >> Huh - this is supposed to come directly from the ACPI tables, so Linux
> > >> and Xen should be using the same source of information.
Both Xen and Linux only see two ACPI overrides (0 & 9) from the
tables. However the Xen logic in mp_config_acpi_legacy_irqs() thinks
IRQ2 is an override
irq 2: irq->mpc_srcbus 0, irq->mpc_srcbusirq 0, irq->mpc_dstapic 2,
intsrc.mpc_dstapic 2
Matches
((irq->mpc_dstapic == intsrc.mpc_dstapic) &&
(irq->mpc_dstirq == i))
i is 2, so irq->mpc_dstirq must be as well.
Regards,
Jason
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-03-04 16:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 7:52 [Xen-devel] [BUG] panic: "IO-APIC + timer doesn't work" - several people have reproduced Aaron Janse
2019-12-31 8:27 ` Andrew Cooper
2019-12-31 9:07 ` Aaron Janse
2020-02-17 19:19 ` Jason Andryuk
2020-02-17 19:46 ` Andrew Cooper
2020-02-17 20:41 ` Jason Andryuk
2020-02-18 1:21 ` Andrew Cooper
2020-02-18 18:43 ` Jason Andryuk
2020-02-18 21:45 ` Andrew Cooper
2020-02-19 8:25 ` Jan Beulich
2020-03-04 16:06 ` Jason Andryuk
2020-03-17 13:48 ` Jason Andryuk
2020-03-17 14:08 ` Jason Andryuk
2020-03-17 14:17 ` Jan Beulich
2020-03-17 14:08 ` Jan Beulich
2020-03-17 14:15 ` Jan Beulich
2020-03-17 15:23 ` Jason Andryuk
2020-03-17 16:31 ` Jason Andryuk
2020-03-18 10:28 ` Jan Beulich
2020-03-18 14:04 ` Jason Andryuk
2020-03-18 17:34 ` Jason Andryuk
2020-04-17 9:31 ` Jan Beulich
2020-04-28 20:59 ` Jason Andryuk
2020-03-04 16:05 ` Jason Andryuk [this message]
2020-01-03 12:51 ` Jan Beulich
2020-01-06 0:35 ` Aaron Janse
2020-01-06 8:57 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKf6xpuRQDvHc6WjrSmaa-NO-++LGVU7Rf+prj0L0DzTjEPh+Q@mail.gmail.com \
--to=jandryuk@gmail.com \
--cc=aaron@ajanse.me \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).