From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: Venkat Duvvuru <VenkatKumar.Duvvuru@Emulex.Com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Gavin Shan <gwshan@linux.vnet.ibm.com>,
Ajit Kumar Khaparde <Ajit.Khaparde@Emulex.Com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] PCI: Mark broken INTx masking for BENET devices
Date: Mon, 12 Jan 2015 09:20:44 +1100 [thread overview]
Message-ID: <20150111222044.GA5446@shangw> (raw)
In-Reply-To: <f588414b-dba0-4d83-942b-0e5841f1e89c@CMEXHTCAS1.ad.emulex.com>
On Fri, Jan 09, 2015 at 07:40:08AM +0000, Venkat Duvvuru wrote:
>> >
>> > Venkat, On IBM's Power7 box, I passed through following adpater to guest
>> with
>> > following
>> ...
>> >
>> > Steps to recreate the issue
>> > ===========================
>> >
>> > 1. Configure the NIC and ping it from external.
>> > 2. Inject EEH error by running following command in host side. After about
>> > 20 seconds, I got following message from host side. With the patch
>> applied
>> > to host kernel, I didn't see the warning messages:
>>
>> This seems really dubious and I don't see any justification at all for declaring
>> DisINTx broken for all devices for the vendor. Typically to call DisINTx broken
>> for a given device, you can just boot the guest with pci=nomsi to force INTx
>> to be used. If that works, then DisINTx masking works. If you require EEH
>> injection to to trigger this, then the problem is more likely some containment
>> issue during EEH recovery. Thanks,
>>
>> Alex
>Yes I agree with Alex.
>pci=nomsi is what exactly we did to see if DisINTx is broken or not and DisINTx works fine in our setup.
>I think, we need to analyze this EEH injection scenario further, to root cause the problem.
>We will post you updates on our findings after the analysis.
Thanks for suggestions. I'll do more experiments to locate the EEH. With the older
QEMU version, I didn't find this issue, so I guess it would be introduced by recent
QEMU VFIO changes.
Note: pci=nomsi didn't give me usable console from the guest side. I don't know why
yet. Need some time to investigate.
Thanks,
Gavin
prev parent reply other threads:[~2015-01-11 22:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 2:17 [PATCH] PCI: Mark broken INTx masking for BENET devices Gavin Shan
2015-01-07 4:29 ` Venkat Duvvuru
2015-01-07 14:57 ` Alex Williamson
2015-01-08 11:33 ` Venkat Duvvuru
2015-01-09 0:33 ` Gavin Shan
2015-01-09 1:25 ` Alex Williamson
2015-01-09 7:40 ` Venkat Duvvuru
2015-01-11 22:20 ` Gavin Shan [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=20150111222044.GA5446@shangw \
--to=gwshan@linux.vnet.ibm.com \
--cc=Ajit.Khaparde@Emulex.Com \
--cc=VenkatKumar.Duvvuru@Emulex.Com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).