From: David Marchand <david.marchand@6wind.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Ferruh Yigit <ferruh.yigit@intel.com>,
stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] drivers: fix vfio kmod dependency
Date: Mon, 22 May 2017 10:27:10 +0200 [thread overview]
Message-ID: <CALwxeUsJ0wEpwxtEiKnrPBSxGmqVsd2jXF6FSwzpzecS7eTG2Q@mail.gmail.com> (raw)
In-Reply-To: <CALwxeUthY9RsW16Mci6QQLHaQaQ7x8oUHDZWUGAgA7xRVU-pwA@mail.gmail.com>
On Mon, May 22, 2017 at 10:25 AM, David Marchand
<david.marchand@6wind.com> wrote:
> On Mon, May 22, 2017 at 10:18 AM, Olivier Matz <olivier.matz@6wind.com> wrote:
>> On Sat, 20 May 2017 15:12:37 +0200, David Marchand <david.marchand@6wind.com> wrote:
>>> vfio is the kernel framework used by the vfio-pci kernel driver.
>>> DPDK drivers do not rely solely on vfio, but rather on vfio-pci to gain
>>> access to pci resources.
>>>
>>> Fixes: 0880c40113ef ("drivers: advertise kmod dependencies in pmdinfo")
>>> Signed-off-by: David Marchand <david.marchand@6wind.com>
>>
>> Acked-by: Olivier Matz <olivier.matz@6wind.com>
>>
>> What would be the impact of not having this fix?
>
> Mainly reporting an incomplete information on the PMD needs.
>
>> I think it would prevent scripts based on pmd modinfo to load the proper
>> kernel module (vfio-pci). So I'd suggest to CC stable. What do you think?
>
> Yes, CCing stable sounds sane to me.
*really* CCing stable ...
--
David Marchand
next parent reply other threads:[~2017-05-22 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1495285957-22307-1-git-send-email-david.marchand@6wind.com>
[not found] ` <20170522101825.7c4b99b6@platinum>
[not found] ` <CALwxeUthY9RsW16Mci6QQLHaQaQ7x8oUHDZWUGAgA7xRVU-pwA@mail.gmail.com>
2017-05-22 8:27 ` David Marchand [this message]
2017-06-05 18:57 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
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=CALwxeUsJ0wEpwxtEiKnrPBSxGmqVsd2jXF6FSwzpzecS7eTG2Q@mail.gmail.com \
--to=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=olivier.matz@6wind.com \
--cc=stable@dpdk.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).