From: Steven Rostedt <rostedt@goodmis.org>
To: Leonid Ravich <leonid.ravich@toganetworks.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
"mingo@redhat.com" <mingo@redhat.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Yigal Korman <yigal.korman@toganetworks.com>,
"linux-trace-kernel@vger.kernel.org"
<linux-trace-kernel@vger.kernel.org>,
Leon Ravich <lravich@gmail.com>
Subject: Re: BUG: ib_mad ftrace event unsupported migration
Date: Wed, 2 Nov 2022 10:20:54 -0400 [thread overview]
Message-ID: <20221102102054.30f5adfc@rorschach.local.home> (raw)
In-Reply-To: <VI1PR02MB623731066685B6E249F71A3189399@VI1PR02MB6237.eurprd02.prod.outlook.com>
On Wed, 2 Nov 2022 14:02:49 +0000
Leonid Ravich <leonid.ravich@toganetworks.com> wrote:
> >I'm guessing some driver's query_pkey op, but AFAIK we don't have any
> >explicit pre-emption reenablements in the code - unless it is sneaky..
> trace infra uses preempt_disable_notrace/preempt_enable_notrace to disable/enable preemtion but my kernel compiled without CONFIG_PREEMPTION so this functions are only barriers - looks like the idea behind was to avoid involuntary preemtion but in our case it is a voluntary (there is a wait_for_completion in the query_pkey rabbit hole).
>
> so no scheduler here to warn about illegal migration.
Well, you should be testing under different configs ;-)
It would have given you the reason for the real bug.
-- Steve
prev parent reply other threads:[~2022-11-02 14:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 10:49 BUG: ib_mad ftrace event unsupported migration Leonid Ravich
2022-11-02 11:44 ` Steven Rostedt
2022-11-02 13:02 ` Jason Gunthorpe
2022-11-02 14:02 ` Leonid Ravich
2022-11-02 14:04 ` Jason Gunthorpe
2022-11-02 14:17 ` Steven Rostedt
2022-11-02 14:24 ` Jason Gunthorpe
2022-11-02 15:59 ` Steven Rostedt
2022-11-02 16:01 ` Jason Gunthorpe
2022-11-02 20:01 ` Leonid Ravich
2022-11-02 22:19 ` Steven Rostedt
2022-11-03 12:22 ` Leonid Ravich
2022-11-03 16:32 ` Steven Rostedt
2022-11-02 14:20 ` Steven Rostedt [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=20221102102054.30f5adfc@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=jgg@ziepe.ca \
--cc=leonid.ravich@toganetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lravich@gmail.com \
--cc=mingo@redhat.com \
--cc=yigal.korman@toganetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.