Re: [dpdk-dev] Windows Draft Build

2020-02-27 Thread David Marchand
On Thu, Feb 27, 2020 at 4:27 PM William Tu wrote: > > > 3. Patch instruction is a bit involved: > > > > * Base on windpdk-v18.08-clang. > > * Import drivers/net/virtio from v18.08 (not attached due to size). > > * Apply windpdk-virtio-1.patch (attached). > > * Apply multi-BAR patches (not attached

Re: [dpdk-dev] Windows Draft Build

2020-02-27 Thread William Tu
> 3. Patch instruction is a bit involved: > > * Base on windpdk-v18.08-clang. > * Import drivers/net/virtio from v18.08 (not attached due to size). > * Apply windpdk-virtio-1.patch (attached). > * Apply multi-BAR patches (not attached due to not being mine). > * Apply windpdk-virtio-2.patch (attach

Re: [dpdk-dev] Windows Draft Build

2020-02-26 Thread Dmitry Kozlyuk
Finally managed to run l2fwd with virtio PMD. Providing details as promised. 1. For some reason, when l2fwd is running, virtual screen stops updating. The system itself is NOT frozen: l2fwd forwards packets, processes can be launched using QEMU guest agent, input is received and processed. Since

Re: [dpdk-dev] Windows Draft Build

2020-02-25 Thread Dmitry Kozlyuk
Hi Ranjit, > This is a very interesting find. Will this change to a custom class allow the > driver to load in the native (bare-metal) case, too? I don't have a DPDK-compatible hardware NIC right now, so I can't perform a complete test. However, I was able to successfully install netUIO with mul

Re: [dpdk-dev] Windows Draft Build

2020-02-25 Thread Ranjit Menon
On 2/24/2020 6:37 PM, Dmitry Kozlyuk wrote: > Oh boy! If DriverEntry() is not being called, the loader is finding something wrong and is unable to load the driver. > > @Harini: Can Jeffrey (@MS) help here? By trial and error I determined that changing device class from "Net" to a custom one fix

Re: [dpdk-dev] Windows Draft Build

2020-02-24 Thread Dmitry Kozlyuk
> Oh boy! If DriverEntry() is not being called, the loader is finding something > wrong and is unable to load the driver. > > @Harini: Can Jeffrey (@MS) help here? By trial and error I determined that changing device class from "Net" to a custom one fixes the issue (see attached patch), root cau

Re: [dpdk-dev] Windows Draft Build

2020-02-18 Thread Ranjit Menon
On 2/16/2020 5:14 PM, Dmitry Kozlyuk wrote: Hi, > "Dpdk.sln" builds OK, will try launching sample apps > a bit later. Netuio driver consistently fails to install on Windows 10 in QEMU with virtio-net (modern interface). Described below is my attempt to install the driver from clean "windpdk-v18

Re: [dpdk-dev] Windows Draft Build

2020-02-16 Thread Dmitry Kozlyuk
Hi, > "Dpdk.sln" builds OK, will try launching sample apps > a bit later. Netuio driver consistently fails to install on Windows 10 in QEMU with virtio-net (modern interface). Described below is my attempt to install the driver from clean "windpdk-v18.08-clang" branch of "dpdk-draft-windows" repo

Re: [dpdk-dev] Windows Draft Build

2020-02-09 Thread Dmitry Kozlyuk
> Did you install the LLVM toolchain for VStudio: > https://marketplace.visualstudio.com/items?itemName=LLVMExtensions.llvm-toolchain > > You will need to ensure VS is closed before installing it. > It says it supports VS2017, but it will also work with VS2019, if VS2017 is > already installed.

Re: [dpdk-dev] Windows Draft Build

2020-02-09 Thread Ranjit Menon
On 2/8/2020 12:45 AM, Dmitry Kozlyuk wrote: Hi, I'm having trouble building "dpdk.sln" from "windpdk-v18.08-clang" branch of "dpdk-draft-windows" repository using Visual Studio 2019 Community Edition. All projects are set up to use some "llvm" toolset. If I install LLVM Build Tools and switch to

[dpdk-dev] Windows Draft Build

2020-02-08 Thread Dmitry Kozlyuk
Hi, I'm having trouble building "dpdk.sln" from "windpdk-v18.08-clang" branch of "dpdk-draft-windows" repository using Visual Studio 2019 Community Edition. All projects are set up to use some "llvm" toolset. If I install LLVM Build Tools and switch toolset to Clang-cl, build fails because Platfor