qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Chao Liu <chao.liu@yeah.net>
Cc: qemu-devel@nongnu.org, bin.meng@windriver.com,
	edgar.iglesias@gmail.com,  alistair@alistair23.me
Subject: Re: [PATCH v2 0/2] Drop ignore_memory_transaction_failures for xilink_zynq
Date: Fri, 27 Sep 2024 13:18:15 +0100	[thread overview]
Message-ID: <CAFEAcA8Kb-ym=Zd1TzcWuqRVbaKAG4TDF3VmZ8EfnBWW-B_Cyg@mail.gmail.com> (raw)
In-Reply-To: <cover.1727425255.git.chao.liu@yeah.net>

On Fri, 27 Sept 2024 at 09:52, Chao Liu <chao.liu@yeah.net> wrote:
>
> Hi, thank you for your prompt reply, it's a great encouragement to me!
>
> Based on your review suggestions, I have improved the v1 patch.
>
> By using create_unimplemented_device() during the initialization phase,
> I added a "znyq.umip" device early on, which covers the 32-bit address space
> of GPA. This can better serve as a replacement for the effect of the
> ignore_memory_transaction_failures flag.
>
> Since create_unimplemented_device() sets the priority of the
> memory region (mr) to -100, normally created devices will override the address
> segments corresponding to the unimplemented devices.
>
> Even if our test set is not sufficiently comprehensive, we can create an
> unimp_device for the maximum address space allowed by the board. This prevents
> the guest system from triggering unexpected exceptions when accessing
> unimplemented devices or regions.

What would be the benefit of doing that? If we're going to
say "we'll make accesses to regions without devices not
generate faults", the simplest way to do that is to
leave the ignore_memory_transaction_failures flag set
the way it is.

thanks
-- PMM


  parent reply	other threads:[~2024-09-27 12:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27  8:51 [PATCH v2 0/2] Drop ignore_memory_transaction_failures for xilink_zynq Chao Liu
2024-09-27  8:51 ` [PATCH v2 1/2] xilink_zynq: Add various missing unimplemented devices Chao Liu
2024-09-27  8:51 ` [PATCH v2 2/2] xilink-zynq-devcfg: Fix up for memory address range size not set correctly Chao Liu
2024-09-27 12:18 ` Peter Maydell [this message]
2024-09-27 14:03   ` [PATCH v2 0/2] Drop ignore_memory_transaction_failures for xilink_zynq Chao Liu
2024-09-27 14:20     ` Peter Maydell
2024-09-27 14:43       ` Chao Liu

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='CAFEAcA8Kb-ym=Zd1TzcWuqRVbaKAG4TDF3VmZ8EfnBWW-B_Cyg@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=alistair@alistair23.me \
    --cc=bin.meng@windriver.com \
    --cc=chao.liu@yeah.net \
    --cc=edgar.iglesias@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).