From: Annie Haramad <annieharamad@gmail.com>
To: qemu-devel@nongnu.org
Subject: Weird behavior in cortex-A7 when disabling/enabling IRQ in ISR
Date: Mon, 22 Feb 2021 17:24:02 +0200 [thread overview]
Message-ID: <CAG-g2dHxmKC76nZO3AJ4Saa93VevUbu7J2r0rBY-FMLP75n0BA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
Hey, I have been running bare metal program on "mcimx7d-sabre" and I have a
weird behavior that doesn't occur on a real hardware or at least I can't
reproduce it on real hardware.
I'm running a basic program that registers interrupt for serial, and then
running in an infinite loop that formatting a string with vsnprintf, in the
ISR I have disabled IRQ Interrupts (CPSID I) handled the interrupt and
enabled IRQ Interrupts (CPISE I). After a while a data abort happens in the
strlen with arg pointer as NULL that called in vsnprintf. When I run the
same code but without the disable/enable IRQ everything works fine. You
have any idea why does it happen?
[-- Attachment #2: Type: text/html, Size: 725 bytes --]
reply other threads:[~2021-02-22 18:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAG-g2dHxmKC76nZO3AJ4Saa93VevUbu7J2r0rBY-FMLP75n0BA@mail.gmail.com \
--to=annieharamad@gmail.com \
--cc=qemu-devel@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).