From: "Qiu, Michael" <michael.qiu@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC] vfio: only map regions VFIO supports
Date: Tue, 14 Jul 2015 11:03:12 +0000 [thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E60286046BACF2@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20150710102448.263257d4@urahara>
Hi, all
While I check the maillist, I found a patch:
[dpdk-dev] [PATCH v3] vfio: Fix overflow while assigning vfio BAR region
offset and size
This patch has fixed this issue :), and will be merged.
This patch is same with mine.
So I will not post the patch again.
Thanks,
Michael
On 7/11/2015 1:24 AM, Stephen Hemminger wrote:
> On Fri, 10 Jul 2015 07:54:10 +0000
> "Qiu, Michael" <michael.qiu@intel.com> wrote:
>
>> Hi, Stephen
>>
>> This patch does not work for fm10k with vfio, see error below:
>>
>> EAL: PCI device 0000:84:00.0 on NUMA socket 1
>> EAL: probe driver: 8086:15a4 rte_pmd_fm10k
>> EAL: PCI memory mapped at 0x7f1980000000
>> EAL: Trying to map BAR 2 that contains the MSI-X table. Trying offsets:
>> 0000:0000, 1000:1000
>> EAL: PCI memory mapped at 0x7f1980401000
>> EAL: pci_map_resource(): cannot mmap(105, 0x7f1980402000, 0x4000000,
>> 0x0): Invalid argument (0xffffffffffffffff)
>> EAL: 0000:84:00.0 mapping BAR4 failed: Invalid argument
>> EAL: Error - exiting with code: 1
>> Cause: Requested device 0000:84:00.0 cannot be used
> Yes. The patch doesn't solve the problem (but might be needed in some future weird hw).
>
>
prev parent reply other threads:[~2015-07-14 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 22:38 Stephen Hemminger
2015-07-10 7:54 ` Qiu, Michael
2015-07-10 17:24 ` Stephen Hemminger
2015-07-14 10:45 ` Qiu, Michael
2015-07-14 11:03 ` Qiu, Michael [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=533710CFB86FA344BFBF2D6802E60286046BACF2@SHSMSX101.ccr.corp.intel.com \
--to=michael.qiu@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).