From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Stafford Horne <shorne@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
openrisc@lists.librecores.org, richard.henderson@linaro.org
Subject: Re: [PATCH v2] hw/openrisc: use right OMPIC size variable
Date: Wed, 4 May 2022 13:10:04 +0200 [thread overview]
Message-ID: <CAHmME9prmCzpg6h-j3o7zUiYzePuegqJOAGSH167H4L-DH=QMg@mail.gmail.com> (raw)
In-Reply-To: <YnGPDumfp1+6DUQG@antec>
On Tue, May 3, 2022 at 10:22 PM Stafford Horne <shorne@gmail.com> wrote:
>
> On Tue, May 03, 2022 at 11:45:33AM +0200, Jason A. Donenfeld wrote:
> > This appears to be a copy and paste error. The UART size was used
> > instead of the much smaller OMPIC size. But actually that smaller OMPIC
> > size is wrong too and doesn't allow the IPI to work in Linux. So set it
> > to the old value.
> >
> > Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> > ---
> > hw/openrisc/openrisc_sim.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/hw/openrisc/openrisc_sim.c b/hw/openrisc/openrisc_sim.c
> > index 99b14940f4..3218db6656 100644
> > --- a/hw/openrisc/openrisc_sim.c
> > +++ b/hw/openrisc/openrisc_sim.c
> > @@ -78,7 +78,7 @@ static const struct MemmapEntry {
> > [OR1KSIM_DRAM] = { 0x00000000, 0 },
> > [OR1KSIM_UART] = { 0x90000000, 0x100 },
> > [OR1KSIM_ETHOC] = { 0x92000000, 0x800 },
> > - [OR1KSIM_OMPIC] = { 0x98000000, 16 },
> > + [OR1KSIM_OMPIC] = { 0x98000000, 0x100 },
>
> Right, I missed this as part of my series. OMPIC will allocate 2 32-bit
> registers per CPU. I documented this here:
>
> - https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/irqchip/irq-ompic.c
>
> I think what we will want here is something like:
>
> [OR1KSIM_OMPIC] = { 0x98000000, 8 * OR1KSIM_CPUS_MAX },
Do you want a v3 or are you going to fix it up yourself?
Jason
next prev parent reply other threads:[~2022-05-04 11:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 23:28 [PATCH] hw/openrisc: use right OMPIC size variable Jason A. Donenfeld
2022-05-02 23:59 ` Richard Henderson
2022-05-03 9:19 ` Stafford Horne
2022-05-03 9:59 ` Jason A. Donenfeld
2022-05-03 9:45 ` [PATCH v2] " Jason A. Donenfeld
2022-05-03 20:22 ` Stafford Horne
2022-05-04 11:10 ` Jason A. Donenfeld [this message]
2022-05-04 22:23 ` Stafford Horne
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='CAHmME9prmCzpg6h-j3o7zUiYzePuegqJOAGSH167H4L-DH=QMg@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=openrisc@lists.librecores.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shorne@gmail.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).