From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Jacob Shin <Jacob.Shin@amd.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] AMD IOMMU: fill msi_desc fields required by commit fe017c59
Date: Wed, 8 May 2013 00:21:05 -0500 [thread overview]
Message-ID: <5189E0C1.2030705@amd.com> (raw)
In-Reply-To: <5189267402000078000D3F03@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 903 bytes --]
On 5/7/2013 9:06 AM, Jan Beulich wrote:
>>>> On 07.05.13 at 15:47, Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
> wrote:
>> On 5/7/2013 2:56 AM, Jan Beulich wrote:
>>>>>> On 07.05.13 at 00:43, Suravee Suthikulanit<suravee.suthikulpanit@amd.com>
>> wrote:
>>>>> This looks fine and tested. Thanks for the patch.
>>> Tested also underneath the multi-vector MSI series? I.e. did the
>>> assertion you were hitting not get triggered anymore with this in
>>> place, as expected?
>>>
>> Yes, I have tested it with the previous set (the x86/IOMMU: multi-vector
>> MSI) that I report the ASSERTION plus the change I made to fix the
>> IOAPIC. With this additional patch, it was no longer asserting since
>> nvec is now 1 (instead of 0 in prior case).
> Which suggests I could put your ack under the AMD patches when
> I resubmit that series after 4.3 got branched?
>
> Jan
>
>
Yes, please do.
Suravee
[-- Attachment #1.2: Type: text/html, Size: 2405 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2013-05-08 5:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 8:34 [PATCH] AMD IOMMU: fill msi_desc fields required by commit fe017c59 Jan Beulich
2013-05-02 14:55 ` Jan Beulich
2013-05-06 22:43 ` Suravee Suthikulanit
2013-05-07 7:56 ` Jan Beulich
2013-05-07 13:47 ` Suravee Suthikulanit
2013-05-07 14:06 ` Jan Beulich
2013-05-08 5:21 ` Suravee Suthikulpanit [this message]
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=5189E0C1.2030705@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=JBeulich@suse.com \
--cc=Jacob.Shin@amd.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.