2015-01-15 13:42, Burakov, Anatoly:
> 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.
No, it's OK. I thin
> > 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 suppor
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 Mon
On 12/19/2014 4:24 PM, Thomas Monjalon wrote:
> 2014-12-19 07:09, Qiu, Michael:
>> Hi Thomas,
>>
>> Will you plan to merge this patch? If yes, you plan to merge it into
>> 1.8 or 2.0?
> It won't be in 1.8 for 2 reasons:
> - there is a risk to break something in some environments, so need more te
2014-12-19 07:09, Qiu, Michael:
> Hi Thomas,
>
> Will you plan to merge this patch? If yes, you plan to merge it into
> 1.8 or 2.0?
It won't be in 1.8 for 2 reasons:
- there is a risk to break something in some environments, so need more tests
- you add a function protoype in eal common withou
Hi Thomas,
Will you plan to merge this patch? If yes, you plan to merge it into
1.8 or 2.0?
Thanks,
Michael
On 12/10/2014 7:48 PM, Burakov, Anatoly wrote:
>> When vfio module is not loaded when kernel support vfio feature, the
>> routine still try to open the container to get file description.
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:
> 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 i
8 matches
Mail list logo
