From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Jacob Shin <jacob.shin@amd.com>,
xiantao.zhang@intel.com, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 0/4] x86/IOMMU: multi-vector MSI prerequisites
Date: Fri, 29 Mar 2013 00:18:36 -0500 [thread overview]
Message-ID: <5155242C.1070803@amd.com> (raw)
In-Reply-To: <51516FA502000078000C86E1@nat28.tlf.novell.com>
Jan,
I found an issue when booting the hypervisor after the patch with
assertion at the line 64 of iommu_intr.c (in function get_intremap_entry).
Stack dump:
...........
get_intremap_entry+0x39/0x58
amd_iommu_read_msi_from_ire+0x74/0xac
iommu_read_msi_from_ire+0x3c/0x3f
set_msi_affinity+0x161/0x1ae
enable_iommu+0x681/0x7d2
amd_iommu_init+0x50b/0x6b1
amd_iov_detect+0x69/0xad
iommu_setup+0x67/0x171
__start_xen+0x278c/0x2b9d
************************************
Panic on CPU 0:
Assertion '(table != NULL) && (offset < INTREMAP_ENTRIES)' failed at
iommu_intr.c:64
*************************************
Investigation showing table is not null and offset = 0.
Suravee
On 3/26/2013 3:51 AM, Jan Beulich wrote:
> 1: IOMMU: allow MSI message to IRTE propagation to fail
> 2: x86/MSI: cleanup to prepare for multi-vector MSI
> 3: AMD IOMMU: allocate IRTE entries instead of using a static mapping
> 4: AMD IOMMU: untie remap and vector maps
>
> Note that especially patch 3 is more RFC-like, as I continue to have
> no way to test this here.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
>
next prev parent reply other threads:[~2013-03-29 5:18 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 8:51 [PATCH 0/4] x86/IOMMU: multi-vector MSI prerequisites Jan Beulich
2013-03-26 9:03 ` [PATCH 1/4] IOMMU: allow MSI message to IRTE propagation to fail Jan Beulich
2013-03-27 11:45 ` George Dunlap
2013-03-27 12:16 ` Jan Beulich
2013-03-27 14:45 ` Boris Ostrovsky
2013-03-27 14:55 ` George Dunlap
2013-03-28 8:25 ` Jan Beulich
2013-03-28 9:46 ` Tim Deegan
2013-03-28 9:49 ` George Dunlap
2013-03-28 10:33 ` George Dunlap
2013-03-28 11:14 ` Jan Beulich
2013-03-28 11:25 ` Tim Deegan
2013-03-28 11:39 ` George Dunlap
2013-03-28 13:47 ` Stefano Stabellini
2013-05-06 20:25 ` Is: git send-email, patch sending, etc Was: " Konrad Rzeszutek Wilk
2013-05-07 8:53 ` Ian Campbell
2013-05-07 9:26 ` Wei Liu
2013-05-07 14:03 ` Konrad Rzeszutek Wilk
2013-03-27 17:26 ` George Dunlap
2013-03-28 8:27 ` Jan Beulich
2013-03-26 9:03 ` [PATCH 2/4] x86/MSI: cleanup to prepare for multi-vector MSI Jan Beulich
2013-03-26 9:04 ` [PATCH 3/4] AMD IOMMU: allocate IRTE entries instead of using a static mapping Jan Beulich
2013-04-02 8:38 ` [PATCH v2 " Jan Beulich
2013-04-11 0:34 ` Suravee Suthikulpanit
2013-03-26 9:05 ` [PATCH 4/4] AMD IOMMU: untie remap and vector maps Jan Beulich
2013-03-28 12:37 ` George Dunlap
2013-03-28 13:09 ` Jan Beulich
2013-03-28 13:40 ` George Dunlap
2013-03-29 5:18 ` Suravee Suthikulpanit [this message]
2013-03-29 5:45 ` [PATCH 0/4] x86/IOMMU: multi-vector MSI prerequisites Suravee Suthikulpanit
2013-04-02 8:39 ` Jan Beulich
2013-04-10 13:55 ` Jan Beulich
2013-04-10 14:38 ` Suravee Suthikulanit
2013-04-10 14:46 ` Jan Beulich
2013-04-11 1:51 ` Suravee Suthikulpanit
2013-04-11 7:13 ` Jan Beulich
2013-04-11 15:40 ` suravee suthikulpanit
2013-04-11 16:11 ` 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=5155242C.1070803@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=JBeulich@suse.com \
--cc=jacob.shin@amd.com \
--cc=xen-devel@lists.xen.org \
--cc=xiantao.zhang@intel.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.