All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Joe Jin <joe.jin@oracle.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Jan Beulich <JBeulich@suse.com>,
	xen-devel@lists.xen.org
Subject: Re: nr_irqs_gsi
Date: Mon, 23 Jul 2012 22:02:01 -0400	[thread overview]
Message-ID: <20120724020201.GC10884@phenom.dumpdata.com> (raw)
In-Reply-To: <500E0265.6090402@oracle.com>

On Tue, Jul 24, 2012 at 10:03:17AM +0800, Joe Jin wrote:
> On 07/23/12 23:34, Konrad Rzeszutek Wilk wrote:
> > On Mon, Jul 23, 2012 at 02:30:37PM +0100, Jan Beulich wrote:
> >>>>> On 12.07.12 at 04:17, Joe Jin <joe.jin@oracle.com> wrote:
> >>>>>> (XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
> >>>>>> (XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
> >>>>>> (XEN) ACPI: IOAPIC (id[0x01] address[0xfec80000] gsi_base[32])
> >>>>>> (XEN) IOAPIC[1]: apic_id 1, version 32, address 0xfec80000, GSI 32-55
> >>>
> >>> Below came from dom0:
> >>>
> >>> ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
> >>> ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
> >>> IOAPIC[0]: apic_id 0, version 255, address 0xfec00000, GSI 0-255
> >>
> >> Now this and ...
> >>
> >>> ACPI: IOAPIC (id[0x01] address[0xfec80000] gsi_base[32])
> >>> IOAPIC[1]: apic_id 1, version 255, address 0xfec80000, GSI 32-287
> >>
> >> ... this is clearly bogus, contradicting what Xen itself prints (see
> >> above).
> > 
> > Yeah, that got fixed up in v3.5 (merge git f08b9c2f8af0d61faa1170aeae4fbca1eff6a504)
> > specifically:
> > 
> >       x86/apic: Fix UP boot crash
> >       xen/apic: implement io apic read with hypercall
> >       xen/x86: Implement x86_apic_ops
> >       x86/apic: Replace io_apic_ops with x86_io_apic_ops.
> >       x86/ioapic: Add io_apic_ops driver layer to allow interception
> > 
> 
> Konrad,
> 
> Would you please point out which commit is make sense for this issue? so far I still
> suspend it's a hypervisor issue rather than dom0 kernel.

I concur. The patches above are just for reporting the GSI properly in the initial domain.

  reply	other threads:[~2012-07-24  2:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11  3:31 nr_irqs_gsi Joe Jin
2012-07-11  9:42 ` nr_irqs_gsi Andrew Cooper
2012-07-11 14:00   ` nr_irqs_gsi Konrad Rzeszutek Wilk
2012-07-12  2:17     ` nr_irqs_gsi Joe Jin
2012-07-12 13:36       ` nr_irqs_gsi Konrad Rzeszutek Wilk
2012-07-23 13:30       ` nr_irqs_gsi Jan Beulich
2012-07-23 15:34         ` nr_irqs_gsi Konrad Rzeszutek Wilk
2012-07-24  2:03           ` nr_irqs_gsi Joe Jin
2012-07-24  2:02             ` Konrad Rzeszutek Wilk [this message]
2012-07-24  2:25               ` nr_irqs_gsi Joe Jin
2012-07-11 23:56   ` nr_irqs_gsi Joe Jin
2012-07-23 13:42     ` nr_irqs_gsi Jan Beulich
2012-07-24  0:21       ` nr_irqs_gsi Joe Jin

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=20120724020201.GC10884@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=joe.jin@oracle.com \
    --cc=xen-devel@lists.xen.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 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.