From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Sam <batmanustc@gmail.com>, dev@dpdk.org, ovs-dev@openvswitch.org
Subject: Re: [dpdk-dev] How to dump DPDK log?
Date: Wed, 16 May 2018 14:29:09 +0100 [thread overview]
Message-ID: <eeec98da-df52-0b9d-f026-e60fd337d572@intel.com> (raw)
In-Reply-To: <CAOE=1Z1ZUz1OHG6iyE7NuTv_qyAMYiZ2__LvrWk4xsr8XGVY+g@mail.gmail.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-16 13:29 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 [this message]
2018-05-17 2:26 ` Sam
2018-05-17 2:41 ` Sam
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=eeec98da-df52-0b9d-f026-e60fd337d572@intel.com \
--to=ferruh.yigit@intel.com \
--cc=batmanustc@gmail.com \
--cc=dev@dpdk.org \
--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).