[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120320204859.GA25944@phenom.dumpdata.com>
Date: Tue, 20 Mar 2012 16:48:59 -0400
From: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To: Suresh Siddha <suresh.b.siddha@...el.com>
Cc: Josh Boyer <jwboyer@...hat.com>, Ingo Molnar <mingo@...e.hu>,
"H. Peter Anvin" <hpa@...or.com>, yinghai@...nel.org,
linux-kernel@...r.kernel.org, kernel-team@...oraproject.org,
midgoon@...il.com
Subject: Re: 3.2.1 Unable to reset IRR messages on boot
On Tue, Mar 20, 2012 at 01:41:32PM -0700, Suresh Siddha wrote:
> On Tue, 2012-03-20 at 16:25 -0400, Konrad Rzeszutek Wilk wrote:
> > On Tue, Mar 20, 2012 at 01:05:19PM -0700, Suresh Siddha wrote:
> > > Also does the dom0 see all the GSI's/io-apic's that the host sees or is
> > > it going to be just one io-apic? I was just wondering if the reg 01 need
> > > to be same as what the host sees?
> >
> > It does not use the APIC mechanism at all. It only needs the GSI value
> > from the IOAPIC and LAPIC so that the ACPI can work.
>
> So the number of redirection entries in the io-apic need to be same as
> the original values then?
It can be up to sixteen and or up to whatever the INT_SRV_OVR has. With
the dummy mapping it was 0xff, which meant it had up to 255 which was more than
enough.
>
> > It could also at startup copy the original values and stick them in these copies.
> > That does mean using the memory allocator to allocate X copies for X IOAPICS. I
> > don't think the memory allocator is active at that stage since we using fixmaps.
> > Thoughts?
>
> You should be able to use alloc_bootmem friends.
>
> thanks,
> suresh
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists