From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Qiu, Michael" <michael.qiu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v6] VFIO: Avoid to enable vfio while the module not loaded
Date: Thu, 15 Jan 2015 13:42:15 +0000 [thread overview]
Message-ID: <C6ECDF3AB251BE4894318F4E4512369780C3CDC1@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <1613897.2bqBHJQoa5@xps13>
Yep, apologies, it's my fault as it was my suggestion. I knew there was a linuxapp-only EAL header, for some reason I thought it's eal_private. Any suggestions on where to put this function? I don't think BSD needs this function.
Thanks,
Anatoly
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Thursday, January 15, 2015 1:38 PM
> To: Qiu, Michael
> Cc: Burakov, Anatoly; dev@dpdk.org; Xie, Huawei
> Subject: Re: [PATCH v6] VFIO: Avoid to enable vfio while the module not
> loaded
>
> > > When vfio module is not loaded when kernel support vfio feature, the
> > > routine still try to open the container to get file description.
> > >
> > > This action is not safe, and of cause got error messages:
> > >
> > > EAL: Detected 40 lcore(s)
> > > EAL: unsupported IOMMU type!
> > > EAL: VFIO support could not be initialized
> > > EAL: Setting up memory...
> > >
> > > This may make user confuse, this patch make it reasonable and much
> > > more soomth to user.
> > >
> > > Signed-off-by: Michael Qiu <michael.qiu@intel.com>
> >
> > Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
>
> Note that rte_eal_check_module has no bsd counterpart.
> It could be needed later.
>
> Applied
>
> Thanks
> --
> Thomas
next prev parent reply other threads:[~2015-01-15 13:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 3:36 [dpdk-dev] [PATCH] " Michael Qiu
2014-12-04 10:00 ` [dpdk-dev] [PATCH v2] " Michael Qiu
2014-12-05 10:00 ` Burakov, Anatoly
2014-12-08 7:25 ` Qiu, Michael
2014-12-08 18:47 ` Burakov, Anatoly
2014-12-09 2:47 ` Qiu, Michael
2014-12-09 9:51 ` Burakov, Anatoly
2014-12-08 8:27 ` [dpdk-dev] [PATCH v3] " Michael Qiu
2014-12-08 9:54 ` Burakov, Anatoly
2014-12-08 10:28 ` Qiu, Michael
2014-12-08 10:44 ` [dpdk-dev] [PATCH v4] " Michael Qiu
2014-12-08 12:19 ` Burakov, Anatoly
2014-12-08 15:28 ` Qiu, Michael
2014-12-10 0:17 ` Xie, Huawei
2014-12-10 2:06 ` Qiu, Michael
2014-12-10 2:22 ` [dpdk-dev] [PATCH v5] " Michael Qiu
2014-12-10 9:21 ` Burakov, Anatoly
2014-12-10 11:29 ` Qiu, Michael
2014-12-10 11:46 ` [dpdk-dev] [PATCH v6] " Michael Qiu
2014-12-10 11:48 ` Burakov, Anatoly
2014-12-19 7:09 ` Qiu, Michael
2014-12-19 8:23 ` Thomas Monjalon
2014-12-22 1:21 ` Qiu, Michael
2015-01-15 13:38 ` Thomas Monjalon
2015-01-15 13:42 ` Burakov, Anatoly [this message]
2015-01-15 13:51 ` Thomas Monjalon
2014-12-04 13:12 ` [dpdk-dev] [PATCH] " Burakov, Anatoly
2014-12-04 13:47 ` Qiu, Michael
2014-12-04 16:31 ` Burakov, Anatoly
2014-12-05 4:01 ` Qiu, Michael
2014-12-04 13:13 ` Burakov, Anatoly
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=C6ECDF3AB251BE4894318F4E4512369780C3CDC1@IRSMSX109.ger.corp.intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=michael.qiu@intel.com \
--cc=thomas.monjalon@6wind.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 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).