From: Paul Burton <paul.burton@mips.com>
To: Chong Qiao <qiaochong@loongson.cn>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <pburton@wavecomp.com>,
James Hogan <jhogan@kernel.org>,
Daniel Thompson <daniel.thompson@linaro.org>,
Douglas Anderson <dianders@chromium.org>,
Will Deacon <will.deacon@arm.com>,
Christophe Leroy <christophe.leroy@c-s.fr>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
QiaoChong <qiaochong@loongson.cn>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: [PATCH] MIPS: KGDB: fix kgdb support for SMP platforms.
Date: Thu, 28 Mar 2019 18:36:27 +0000 [thread overview]
Message-ID: <CY4PR2201MB1272AF54E406FAF07A6FAAFFC1590@CY4PR2201MB1272.namprd22.prod.outlook.com> (raw)
In-Reply-To: <20190327230801.3650-1-qiaochong@loongson.cn>
Hello,
Chong Qiao wrote:
> KGDB_call_nmi_hook is called by other cpu through smp call.
> MIPS smp call is processed in ipi irq handler and regs is saved in
> handle_int.
> So kgdb_call_nmi_hook get regs by get_irq_regs and regs will be passed
> to kgdb_cpu_enter.
>
> Signed-off-by: Chong Qiao <qiaochong@loongson.cn>
> Reviewed-by: Douglas Anderson <dianders@chromium.org>
> Acked-by: Daniel Thompson <daniel.thompson@linaro.org>
Applied to mips-fixes.
Thanks,
Paul
[ This message was auto-generated; if you believe anything is incorrect
then please email paul.burton@mips.com to report it. ]
next prev parent reply other threads:[~2019-03-28 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 23:08 Chong Qiao
2019-03-27 23:15 ` Doug Anderson
2019-03-28 7:06 ` Daniel Thompson
2019-03-28 18:36 ` Paul Burton [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-27 15:05 qiaochong
2019-03-27 16:25 ` Doug Anderson
2019-03-27 22:25 ` qiaochong
2019-03-27 22:27 ` Doug Anderson
2019-03-28 7:03 ` Daniel Thompson
2019-03-27 13:17 qiaochong
2019-03-27 14:37 ` Doug Anderson
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=CY4PR2201MB1272AF54E406FAF07A6FAAFFC1590@CY4PR2201MB1272.namprd22.prod.outlook.com \
--to=paul.burton@mips.com \
--cc=christophe.leroy@c-s.fr \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=pburton@wavecomp.com \
--cc=qiaochong@loongson.cn \
--cc=ralf@linux-mips.org \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®