From: Idan Horowitz <idan.horowitz@gmail.com>
To: Atish Patra <atishp@atishpatra.org>
Cc: Alistair Francis <Alistair.Francis@wdc.com>,
phantom@zju.edu.cn, "open list:RISC-V" <qemu-riscv@nongnu.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] target/riscv: Exit current TB after an sfence.vma
Date: Wed, 30 Mar 2022 09:15:03 +0300 [thread overview]
Message-ID: <CA+4MfE+hFQhRYEgEXy-u10=MBhnmA5f7MdRFjW7Xc0dLPSiLXw@mail.gmail.com> (raw)
In-Reply-To: <CAOnJCUJck5o_-cayf-=mccenoZH048+2zhGDGOoWKiVMUFWWmQ@mail.gmail.com>
On Wed, 30 Mar 2022 at 02:16, Atish Patra <atishp@atishpatra.org> wrote:
>
> This is in for-next on Alistair's tree and fails to boot the kernel
> with the following error (found -d in_asm mode).
> Reverting the patch solves the issue.
>
> ----------------
> IN:
> Priv: 1; Virt: 0
> 0x0000000080201040: 18051073 csrrw zero,satp,a0
>
> ----------------
> IN:
> Priv: 1; Virt: 0
> 0x0000000080201044: Address 0x80201044 is out of bounds.
>
> 0x0000000080201049: Address 0x80201049 is out of bounds.
>
> 0x000000008020104e: Address 0x8020104e is out of bounds.
>
> Disassembler disagrees with translator over instruction decoding
> Please report this to qemu-devel@nongnu.org
>
> ----------------
> IN:
> Priv: 1; Virt: 0
> 0x0000000080201050: Address 0x80201050 is out of bounds.
>
> 0x0000000080201055: Address 0x80201055 is out of bounds.
>
> 0x000000008020105a: Address 0x8020105a is out of bounds.
>
> Disassembler disagrees with translator over instruction decoding
> Please report this to qemu-devel@nongnu.org
>
> ----------------
> IN:
> Priv: 1; Virt: 0
> 0x000000008020105c: Address 0x8020105c is out of bounds.
>
> Disassembler disagrees with translator over instruction decoding
> Please report this to qemu-devel@nongnu.org
>
> --
> Regards,
> Atish
Do you have more specific information about which kernel image doesn't boot?
The errors you're seeing simply mean that these addresses are not
translated by the new address translation context set by the write to
the satp.
To be honest I don't immediately see how this could be caused by the
patch, as it modifies the behaviour of the sfence.vma instruction, and
there are none in your trace.
Idan Horowitz
WARNING: multiple messages have this Message-ID (diff)
From: Idan Horowitz <idan.horowitz@gmail.com>
To: Atish Patra <atishp@atishpatra.org>
Cc: phantom@zju.edu.cn, "open list:RISC-V" <qemu-riscv@nongnu.org>,
Alistair Francis <Alistair.Francis@wdc.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] target/riscv: Exit current TB after an sfence.vma
Date: Wed, 30 Mar 2022 09:15:03 +0300 [thread overview]
Message-ID: <CA+4MfE+hFQhRYEgEXy-u10=MBhnmA5f7MdRFjW7Xc0dLPSiLXw@mail.gmail.com> (raw)
In-Reply-To: <CAOnJCUJck5o_-cayf-=mccenoZH048+2zhGDGOoWKiVMUFWWmQ@mail.gmail.com>
On Wed, 30 Mar 2022 at 02:16, Atish Patra <atishp@atishpatra.org> wrote:
>
> This is in for-next on Alistair's tree and fails to boot the kernel
> with the following error (found -d in_asm mode).
> Reverting the patch solves the issue.
>
> ----------------
> IN:
> Priv: 1; Virt: 0
> 0x0000000080201040: 18051073 csrrw zero,satp,a0
>
> ----------------
> IN:
> Priv: 1; Virt: 0
> 0x0000000080201044: Address 0x80201044 is out of bounds.
>
> 0x0000000080201049: Address 0x80201049 is out of bounds.
>
> 0x000000008020104e: Address 0x8020104e is out of bounds.
>
> Disassembler disagrees with translator over instruction decoding
> Please report this to qemu-devel@nongnu.org
>
> ----------------
> IN:
> Priv: 1; Virt: 0
> 0x0000000080201050: Address 0x80201050 is out of bounds.
>
> 0x0000000080201055: Address 0x80201055 is out of bounds.
>
> 0x000000008020105a: Address 0x8020105a is out of bounds.
>
> Disassembler disagrees with translator over instruction decoding
> Please report this to qemu-devel@nongnu.org
>
> ----------------
> IN:
> Priv: 1; Virt: 0
> 0x000000008020105c: Address 0x8020105c is out of bounds.
>
> Disassembler disagrees with translator over instruction decoding
> Please report this to qemu-devel@nongnu.org
>
> --
> Regards,
> Atish
Do you have more specific information about which kernel image doesn't boot?
The errors you're seeing simply mean that these addresses are not
translated by the new address translation context set by the write to
the satp.
To be honest I don't immediately see how this could be caused by the
patch, as it modifies the behaviour of the sfence.vma instruction, and
there are none in your trace.
Idan Horowitz
next prev parent reply other threads:[~2022-03-30 6:36 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 17:22 [PATCH] target/riscv: Exit current TB after an sfence.vma phantom
2022-03-29 23:15 ` Atish Patra
2022-03-29 23:15 ` Atish Patra
2022-03-30 6:15 ` Idan Horowitz [this message]
2022-03-30 6:15 ` Idan Horowitz
2022-03-30 7:28 ` Atish Patra
2022-03-30 7:28 ` Atish Patra
2022-03-30 7:35 ` Idan Horowitz
2022-03-30 7:35 ` Idan Horowitz
2022-03-30 12:38 ` phantom
2022-03-30 12:38 ` phantom
2022-03-30 16:11 ` Palmer Dabbelt
2022-03-30 16:11 ` Palmer Dabbelt
2022-03-30 16:11 ` Palmer Dabbelt
2022-03-30 17:06 ` Palmer Dabbelt
2022-03-30 17:06 ` Palmer Dabbelt
2022-03-30 17:06 ` Palmer Dabbelt
2022-03-30 17:10 ` Idan Horowitz
2022-03-30 17:10 ` Idan Horowitz
2022-03-30 17:10 ` Idan Horowitz
2022-03-31 3:23 ` Alistair Francis
2022-03-31 3:23 ` Alistair Francis
2022-03-31 3:23 ` Alistair Francis
2022-03-31 4:36 ` Palmer Dabbelt
2022-03-31 4:36 ` Palmer Dabbelt
2022-03-31 4:36 ` Palmer Dabbelt
2022-03-31 5:13 ` Alistair Francis
2022-03-31 5:13 ` Alistair Francis
2022-03-31 5:13 ` Alistair Francis
2022-03-31 19:54 ` Palmer Dabbelt
2022-03-31 19:54 ` Palmer Dabbelt
2022-03-31 19:54 ` Palmer Dabbelt
-- strict thread matches above, loose matches on Subject: below --
2022-03-15 19:23 Idan Horowitz
2022-03-15 19:23 ` Idan Horowitz
2022-03-15 19:37 ` Richard Henderson
2022-03-15 19:37 ` Richard Henderson
2022-03-15 22:52 ` Alistair Francis
2022-03-15 22:52 ` Alistair Francis
2022-03-15 23:42 ` Alistair Francis
2022-03-15 23:42 ` Alistair Francis
2022-03-30 6:09 ` Alistair Francis
2022-03-30 6:09 ` Alistair Francis
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='CA+4MfE+hFQhRYEgEXy-u10=MBhnmA5f7MdRFjW7Xc0dLPSiLXw@mail.gmail.com' \
--to=idan.horowitz@gmail.com \
--cc=Alistair.Francis@wdc.com \
--cc=atishp@atishpatra.org \
--cc=phantom@zju.edu.cn \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@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 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.