All of lore.kernel.org
 help / color / mirror / Atom feed
From: schspa <schspa@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: "Eduardo Habkost" <ehabkost@redhat.com>,
	"Kevin Zhao" <kevin.zhao@linaro.org>,
	"Alistair Francis" <alistair@alistair23.me>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	qemu-arm <qemu-arm@nongnu.org>,
	"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [PATCH] arm: xlnx-versal: fix virtio-mmio base address assignment
Date: Thu, 25 Feb 2021 14:35:57 +0800	[thread overview]
Message-ID: <aca79b9768aeae38512a35924aaad1a7c33368ea.camel@gmail.com> (raw)
In-Reply-To: <CAFEAcA_W0AhNYs7+9hn1H6B2DL+UnSdhrj2JsBS4vCZ6fEd_pw@mail.gmail.com>

On Mon, 2021-02-08 at 12:59 +0000, Peter Maydell wrote:
> I just suggested something on another thread: call
> memory_region_find()
> and then look at the offset_within_address_space field of the
> returned
> MemoryRegionSection. I think that should get you the offset of the
> transport within the system address space regardless of how much
> use of containers and other oddball mappings are involved. (If the
> transport is not mapped into the system address space at all then
> you'll get its offset within whatever that other address space is,
> but I think we can reasonably ignore that unlikely corner case.)


Thanks for your suggestions, I have tried it on both arm virt & the
Xilinx platform works perfectly.

I have upload a new patch v4 for it.
-- 
schspa <schspa@gmail.com>


      parent reply	other threads:[~2021-02-25  6:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04  6:58 [PATCH] arm: xlnx-versal: fix virtio-mmio base address assignment schspa
2021-02-04  8:19 ` Philippe Mathieu-Daudé
2021-02-04  8:19   ` Philippe Mathieu-Daudé
2021-02-04  9:04   ` schspa
2021-02-05  7:53     ` Philippe Mathieu-Daudé
2021-02-05  7:53       ` Philippe Mathieu-Daudé
2021-02-05 10:03       ` Peter Maydell
2021-02-05 10:03         ` Peter Maydell
2021-02-05 10:31         ` Philippe Mathieu-Daudé
2021-02-05 11:18           ` Peter Maydell
2021-02-05 14:08             ` Edgar E. Iglesias
2021-02-08  5:34               ` schspa
2021-02-08 11:57                 ` Laszlo Ersek
2021-02-08 12:59               ` Peter Maydell
2021-02-25  5:36                 ` [PATCH v4] virtio-mmio: improve virtio-mmio get_dev_path alog schspa
2021-03-05 11:57                   ` Peter Maydell
2021-03-06  2:28                     ` Shi Schspa
2021-02-25  6:35                 ` schspa [this message]

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=aca79b9768aeae38512a35924aaad1a7c33368ea.camel@gmail.com \
    --to=schspa@gmail.com \
    --cc=alistair@alistair23.me \
    --cc=armbru@redhat.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=ehabkost@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=kevin.zhao@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --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 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.