From: David Miller <davem@davemloft.net>
To: xiliang@redhat.com
Cc: netdev@vger.kernel.org, xen-devel@lists.xenproject.org,
jgross@suse.com, boris.ostrovsky@oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3] xen-netfront: fix warn message as irq device name has '/'
Date: Tue, 14 Aug 2018 10:11:02 -0700 (PDT) [thread overview]
Message-ID: <20180814.101102.975738099798437246.davem@davemloft.net> (raw)
In-Reply-To: <20180814152128.5477-1-xiliang@redhat.com>
From: Xiao Liang <xiliang@redhat.com>
Date: Tue, 14 Aug 2018 23:21:28 +0800
> There is a call trace generated after commit 2d408c0d4574b01b9ed45e02516888bf925e11a9(
> xen-netfront: fix queue name setting). There is no 'device/vif/xx-q0-tx' file found
> under /proc/irq/xx/.
>
> This patch only picks up device type and id as its name.
>
> With the patch, now /proc/interrupts looks like below and the warning message gone:
> 70: 21 0 0 0 xen-dyn -event vif0-q0-tx
> 71: 15 0 0 0 xen-dyn -event vif0-q0-rx
> 72: 14 0 0 0 xen-dyn -event vif0-q1-tx
> 73: 33 0 0 0 xen-dyn -event vif0-q1-rx
> 74: 12 0 0 0 xen-dyn -event vif0-q2-tx
> 75: 24 0 0 0 xen-dyn -event vif0-q2-rx
> 76: 19 0 0 0 xen-dyn -event vif0-q3-tx
> 77: 21 0 0 0 xen-dyn -event vif0-q3-rx
>
> Below is call trace information without this patch:
...
> Signed-off-by: Xiao Liang <xiliang@redhat.com>
> Reviewed-by: Juergen Gross <jgross@suse.com>
Applied, thank you.
prev parent reply other threads:[~2018-08-14 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 15:21 [PATCH net-next v3] xen-netfront: fix warn message as irq device name has '/' Xiao Liang
2018-08-14 17:11 ` David Miller [this message]
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=20180814.101102.975738099798437246.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xiliang@redhat.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).