From mboxrd@z Thu Jan  1 00:00:00 1970
From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: Regression with Xen 4.4 when booting with AMD IOMMU
 on TA890FXE BIOSTAR
Date: Tue, 24 Dec 2013 17:20:55 -0600
Message-ID: <52BA16D7.3090008@amd.com>
References: <20131219182519.GA6479@pegasus.dumpdata.com>
	<52B33D32.1080101@citrix.com>
	<20131219185211.GA8224@andromeda.dapyr.net>
	<52B3626B.7050607@oracle.com>
	<20131220024312.GI25322@phenom.dumpdata.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Suravee.Suthikulpanit@amd.com>) id 1VvbHe-0002H1-5N
	for xen-devel@lists.xenproject.org; Tue, 24 Dec 2013 23:21:06 +0000
In-Reply-To: <20131220024312.GI25322@phenom.dumpdata.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Konrad Rzeszutek Wilk <konrad@darnok.org>, "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>, "jbeulich@suse.com" <jbeulich@suse.com>, Andrew Cooper <andrew.cooper3@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On 12/19/2013 8:43 PM, Konrad Rzeszutek Wilk wrote:
>>> (XEN) AMD-Vi: per-device vector map logic is broken.  Using per-device-global maps instead until a fix is found.
>>
>> Looks like IOAPIC definition is missing from IVRS. The one that's
>> listed (0000:00:00.1 variety 0x1 handle 0x6) is usually unused IIRC.
>> I'd expect an entry for the second one (that lives on the
>> southbridge), such as
>>      AMD-Vi: IVHD Special: 0000:00:14.0 variety 0x1 handle 0
>>
>> And page faults that you are seeing may also be related to this
>> since 0xa0 is 00:14.0.
>>
>> BIOS update might help with this problem (looks like Biostar has a
>> newer BIOS for this board) but I think this should be fixed so maybe
>> you want to keep this BIOS until a fix is developed.
>
> OK.
>>
>> You could try booting with iommu=no-intremap to work around this in
>> the meantime.
>
> That did make it boot. Thanks!
>

I can reproduce the issue also and I am looking into this. I will update 
once I found the issue.

Suravee