From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Keir (Xen.org)" <keir@xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>
Subject: Re: [xen-unstable test] 11946: regressions - FAIL
Date: Mon, 7 May 2012 16:51:31 +0100 [thread overview]
Message-ID: <4FA7EF83.3030902@citrix.com> (raw)
In-Reply-To: <4FA7FE2C02000078000820A6@nat28.tlf.novell.com>
On 07/05/2012 15:54, Jan Beulich wrote:
>>>> On 07.05.12 at 16:41, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> It appears we have two functions to dump the IO-APIC state:
>> __print_IO_APIC() which gets called on boot and from 'z', and
>> dump_ioapic_irq_info() which gets called from the end of 'i'. These
>> should probably be consolidated somehow.
> Rather not - 'z' provides information on the IO-APIC that isn't
> directly related to specific interrupts, while 'i' (when it comes to
> the IO-APIC) is exclusively interested in the RTEs. Unless
> dump_ioapic_irq_info() is _fully_ redundant with 'z' (didn't check
> in detail yet), in which case I'd vote for removing this function.
>
> Jan
>
dump_ioapic_irq_info() loops through nr_irqs_gsi and uses irq_2_pin to
work out which io-apic RTE to read and decode.
__print_IO_APIC() loop through nr_ioapics, then through each RTE and
decodes it. At the end, it loops through nr_irqs_gsi and matches irqs
to ioapic:pin pairs.
So they are probably different enough to be worth keeping.
~Andrew
next prev parent reply other threads:[~2012-05-07 15:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 20:16 [xen-unstable test] 11946: regressions - FAIL xen.org
2012-02-14 10:44 ` Ian Campbell
2012-02-14 19:17 ` Daniel De Graaf
2012-03-27 10:36 ` Ian Campbell
2012-03-27 10:52 ` Jan Beulich
2012-05-04 19:48 ` AP
2012-05-04 20:11 ` Andrew Cooper
2012-05-05 0:21 ` AP
2012-05-05 11:04 ` Andrew Cooper
2012-05-05 18:41 ` AP
2012-05-05 19:06 ` AP
2012-05-07 8:10 ` Jan Beulich
2012-05-07 11:50 ` Andrew Cooper
2012-05-07 13:34 ` Jan Beulich
2012-05-07 14:41 ` Andrew Cooper
2012-05-07 14:50 ` Jan Beulich
2012-05-07 15:40 ` Andrew Cooper
2012-05-07 15:43 ` Jan Beulich
2012-05-07 14:54 ` Jan Beulich
2012-05-07 15:51 ` Andrew Cooper [this message]
2012-05-07 18:29 ` AP
2012-05-08 6:37 ` Jan Beulich
2012-05-05 10:33 ` Ian Campbell
2012-05-05 11:11 ` Andrew Cooper
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=4FA7EF83.3030902@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=keir@xen.org \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.