From: Sam <batmanustc@gmail.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, ovs-dev@openvswitch.org
Subject: Re: [dpdk-dev] How to dump DPDK log?
Date: Thu, 17 May 2018 10:41:52 +0800 [thread overview]
Message-ID: <CAOE=1Z0PTKM3vWDqwTs7nw=YpnuKoB6uOPho=tf5Ad5q5xhf5A@mail.gmail.com> (raw)
In-Reply-To: <CAOE=1Z2wPYgWy9-R00pRrLau3D6DdmmM7Keppua8kEipt9TKgA@mail.gmail.com>
Oh, it should be user1,8 in dpdk-17.05
OMG....
2018-05-17 10:26 GMT+08:00 Sam <batmanustc@gmail.com>:
> How to set this param...
>
> I use this, but report me bug:
>
> sudo /usr/local/bin/ovs-vsctl --no-wait set Open_vSwitch .
> other_config:dpdk-extra="--log-level=user1,debug -c 0x40004 -n 4
> --socket-mem 1024 -w 0000:01:00.0 -w 0000:01:00.1"
>
> Bug:
>
> 2018-05-17T02:23:21.878Z|00010|dpdk|INFO|EAL ARGS: ovs-vswitchd
> --log-level=user1,debug -c 0x40004 -n 4 --socket-mem 1024 -w 0000:01:00.0
> -w 0000:01:00.1
> 2018-05-17T02:23:21.878Z|00011|dpdk|ERR|EAL: invalid parameters for
> --log-level
> 2018-05-17T02:23:21.879Z|00012|dpdk|INFO|EAL: Detected 32 lcore(s)
> 2018-05-17T02:23:21.879Z|00013|dpdk|ERR|EAL: invalid parameters for
> --log-level
>
> 2018-05-17T02:23:04.374Z|00010|dpdk|INFO|EAL ARGS: ovs-vswitchd
> --log-level="user1,debug" -c 0x40004 -n 4 --socket-mem 1024 -w 0000:01:00.0
> -w 0000:01:00.1
> 2018-05-17T02:23:04.374Z|00011|dpdk|ERR|EAL: invalid parameters for
> --log-level
> 2018-05-17T02:23:04.375Z|00012|dpdk|INFO|EAL: Detected 32 lcore(s)
> 2018-05-17T02:23:04.375Z|00013|dpdk|ERR|EAL: invalid parameters for
> --log-level
>
> 2018-05-16 21:29 GMT+08:00 Ferruh Yigit <ferruh.yigit@intel.com>:
>
>> On 5/16/2018 9:30 AM, Sam wrote:
>> > I want DPDK VHOST module DEBUG level log
>> >
>> > 2018-05-16 16:27 GMT+08:00 Sam <batmanustc@gmail.com>:
>> >
>> >> Hi all,
>> >>
>> >> I'm debugging OVS2.9.0 and DPDK18.02, I found I could not dump DPDK log
>> >> like vhost module.
>> >>
>> >> How can I dump DPDK log into files? Thank you~
>> >>
>>
>> (Unfortunately) vhost module doesn't register its log type but uses USER1
>> log
>> type [1].
>>
>> Need to set user1 log type to debug, following eal parameter should work:
>> --log-level="user1,debug"
>>
>> Same can be done with logging related APIs by application
>>
>>
>> [1]
>> https://dpdk.org/browse/dpdk/tree/lib/librte_vhost/vhost.h?h
>> =v18.05-rc4#n351
>>
>
>
next prev parent reply other threads:[~2018-05-17 2:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 8:27 Sam
2018-05-16 8:30 ` Sam
2018-05-16 13:29 ` Ferruh Yigit
2018-05-17 2:26 ` Sam
2018-05-17 2:41 ` Sam [this message]
2018-05-17 9:15 ` Ferruh Yigit
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='CAOE=1Z0PTKM3vWDqwTs7nw=YpnuKoB6uOPho=tf5Ad5q5xhf5A@mail.gmail.com' \
--to=batmanustc@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ovs-dev@openvswitch.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).