qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alistair Francis <alistair23@gmail.com>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
	alistair.francis@wdc.com,  bmeng@tinylab.org,
	liwei1518@gmail.com, zhiwei_liu@linux.alibaba.com,
	 palmer@rivosinc.com, richard.henderson@linaro.org
Subject: Re: [PATCH v3 0/2] target/riscv: throw debug exception before page fault
Date: Wed, 29 Jan 2025 11:48:10 +1000	[thread overview]
Message-ID: <CAKmqyKN-+Jo0Hoexk5Up=DBiHqmB_6-SK87Gwx-+bEORoAwQQQ@mail.gmail.com> (raw)
In-Reply-To: <20250121170626.1992570-1-dbarboza@ventanamicro.com>

On Wed, Jan 22, 2025 at 3:07 AM Daniel Henrique Barboza
<dbarboza@ventanamicro.com> wrote:
>
> Hi,
>
> In this new version, in patch 2,  we're using the address 'size' val from
> riscv_cpu_tlb_fill() instead of infering it from the CPU XLEN.
>
> No other changes made. Patches based on master.
>
> Changes from v2:
> - patch 2:
>   - use 'size' instead of infering wp_len using the CPU XLEN
> - v2 link: https://lore.kernel.org/qemu-riscv/20250120204910.1317013-1-dbarboza@ventanamicro.com/
>
> Daniel Henrique Barboza (2):
>   target/riscv/debug.c: use wp size = 4 for 32-bit CPUs
>   target/riscv: throw debug exception before page fault

Thanks!

Applied to riscv-to-apply.next

Alistair

>
>  target/riscv/cpu_helper.c | 18 ++++++++++++++++++
>  target/riscv/debug.c      |  6 ++++--
>  2 files changed, 22 insertions(+), 2 deletions(-)
>
> --
> 2.47.1
>
>


  parent reply	other threads:[~2025-01-29  1:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21 17:06 [PATCH v3 0/2] target/riscv: throw debug exception before page fault Daniel Henrique Barboza
2025-01-21 17:06 ` [PATCH v3 1/2] target/riscv/debug.c: use wp size = 4 for 32-bit CPUs Daniel Henrique Barboza
2025-01-21 18:22   ` Philippe Mathieu-Daudé
2025-01-29  1:40   ` Alistair Francis
2025-01-21 17:06 ` [PATCH v3 2/2] target/riscv: throw debug exception before page fault Daniel Henrique Barboza
2025-01-21 23:13   ` Richard Henderson
2025-01-29  1:46   ` Alistair Francis
2025-01-29  1:48 ` Alistair Francis [this message]
2025-03-06  6:33 ` [PATCH v3 0/2] " Michael Tokarev
2025-03-06  7:44   ` 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='CAKmqyKN-+Jo0Hoexk5Up=DBiHqmB_6-SK87Gwx-+bEORoAwQQQ@mail.gmail.com' \
    --to=alistair23@gmail.com \
    --cc=alistair.francis@wdc.com \
    --cc=bmeng@tinylab.org \
    --cc=dbarboza@ventanamicro.com \
    --cc=liwei1518@gmail.com \
    --cc=palmer@rivosinc.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=zhiwei_liu@linux.alibaba.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).