From: Fabiano Rosas <farosas@linux.ibm.com>
To: "Bin Meng" <bmeng.cn@gmail.com>,
"Cédric Le Goater" <clg@kaod.org>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Greg Kurz" <groug@kaod.org>
Cc: Bin Meng <bin.meng@windriver.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v2] target/ppc: Fix BookE debug interrupt generation
Date: Fri, 22 Apr 2022 09:17:51 -0300 [thread overview]
Message-ID: <87o80tjor4.fsf@linux.ibm.com> (raw)
In-Reply-To: <20220421011729.1148727-1-bmeng.cn@gmail.com>
Bin Meng <bmeng.cn@gmail.com> writes:
> From: Bin Meng <bin.meng@windriver.com>
>
> Per E500 core reference manual [1], chapter 8.4.4 "Branch Taken Debug
> Event" and chapter 8.4.5 "Instruction Complete Debug Event":
>
> "A branch taken debug event occurs if both MSR[DE] and DBCR0[BRT]
> are set ... Branch taken debug events are not recognized if MSR[DE]
> is cleared when the branch instruction executes."
>
> "An instruction complete debug event occurs when any instruction
> completes execution so long as MSR[DE] and DBCR0[ICMP] are both
> set ... Instruction complete debug events are not recognized if
> MSR[DE] is cleared at the time of the instruction execution."
>
> Current codes do not check MSR.DE bit before setting HFLAGS_SE and
> HFLAGS_BE flag, which would cause the immediate debug interrupt to
> be generated, e.g.: when DBCR0.ICMP bit is set by guest software
> and MSR.DE is not set.
>
> [1] https://www.nxp.com/docs/en/reference-manual/E500CORERM.pdf
>
> Signed-off-by: Bin Meng <bin.meng@windriver.com>
Reviewed-by: Fabiano Rosas <farosas@linux.ibm.com>
next prev parent reply other threads:[~2022-04-22 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 1:17 [PATCH v2] target/ppc: Fix BookE debug interrupt generation Bin Meng
2022-04-21 6:23 ` Cédric Le Goater
2022-04-22 12:17 ` Fabiano Rosas [this message]
2022-04-25 14:16 ` Lucas Mateus Martins Araujo e Castro
2022-04-25 14:47 ` Cédric Le Goater
2022-04-26 19:13 ` Daniel Henrique Barboza
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=87o80tjor4.fsf@linux.ibm.com \
--to=farosas@linux.ibm.com \
--cc=bin.meng@windriver.com \
--cc=bmeng.cn@gmail.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).