From: "Cédric Le Goater" <clg@kaod.org>
To: Peter Delevoryas <pdel@fb.com>
Cc: <peter.maydell@linaro.org>, <andrew@aj.id.au>, <joel@jms.id.au>,
<pbonzini@redhat.com>, <berrange@redhat.com>,
<eduardo@habkost.net>, <"i.mitsyanko@gmail.com.mst"@redhat.com>,
<marcel.apfelbaum@gmail.com>, <richard.henderson@linaro.org>,
<f4bug@amsat.org>, <ani@anisinha.ca>, <qemu-devel@nongnu.org>,
<qemu-arm@nongnu.org>, <kvm@vger.kernel.org>
Subject: Re: [PATCH 01/14] sysbus: Remove sysbus_mmio_unmap
Date: Thu, 23 Jun 2022 17:09:44 +0200 [thread overview]
Message-ID: <faba2fe7-0296-2e76-9f20-e41e159f359d@kaod.org> (raw)
In-Reply-To: <20220623095825.2038562-2-pdel@fb.com>
On 6/23/22 11:58, Peter Delevoryas wrote:
> Cedric removed usage of this function in a previous commit.
>
> Fixes: 981b1c6266c6 ("spapr/xive: rework the mapping the KVM memory regions")
> Signed-off-by: Peter Delevoryas <pdel@fb.com>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Thanks,
C.
> ---
> hw/core/sysbus.c | 10 ----------
> include/hw/sysbus.h | 1 -
> 2 files changed, 11 deletions(-)
>
> diff --git a/hw/core/sysbus.c b/hw/core/sysbus.c
> index 05c1da3d31..637e18f247 100644
> --- a/hw/core/sysbus.c
> +++ b/hw/core/sysbus.c
> @@ -154,16 +154,6 @@ static void sysbus_mmio_map_common(SysBusDevice *dev, int n, hwaddr addr,
> }
> }
>
> -void sysbus_mmio_unmap(SysBusDevice *dev, int n)
> -{
> - assert(n >= 0 && n < dev->num_mmio);
> -
> - if (dev->mmio[n].addr != (hwaddr)-1) {
> - memory_region_del_subregion(get_system_memory(), dev->mmio[n].memory);
> - dev->mmio[n].addr = (hwaddr)-1;
> - }
> -}
> -
> void sysbus_mmio_map(SysBusDevice *dev, int n, hwaddr addr)
> {
> sysbus_mmio_map_common(dev, n, addr, false, 0);
> diff --git a/include/hw/sysbus.h b/include/hw/sysbus.h
> index 3564b7b6a2..153ef20695 100644
> --- a/include/hw/sysbus.h
> +++ b/include/hw/sysbus.h
> @@ -82,7 +82,6 @@ qemu_irq sysbus_get_connected_irq(SysBusDevice *dev, int n);
> void sysbus_mmio_map(SysBusDevice *dev, int n, hwaddr addr);
> void sysbus_mmio_map_overlap(SysBusDevice *dev, int n, hwaddr addr,
> int priority);
> -void sysbus_mmio_unmap(SysBusDevice *dev, int n);
> void sysbus_add_io(SysBusDevice *dev, hwaddr addr,
> MemoryRegion *mem);
> MemoryRegion *sysbus_address_space(SysBusDevice *dev);
next prev parent reply other threads:[~2022-06-23 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220623095825.2038562-1-pdel@fb.com>
[not found] ` <20220623095825.2038562-2-pdel@fb.com>
2022-06-23 12:09 ` [PATCH 01/14] sysbus: Remove sysbus_mmio_unmap Peter Maydell
2022-06-23 15:09 ` Cédric Le Goater [this message]
[not found] ` <20220623095825.2038562-7-pdel@fb.com>
2022-06-23 12:30 ` [PATCH 06/14] aspeed: Add system-memory QOM link to SoC Peter Maydell
2022-06-23 18:30 ` Peter Delevoryas
[not found] ` <20220623095825.2038562-12-pdel@fb.com>
2022-06-23 12:56 ` [PATCH 11/14] aspeed: Switch to create_unimplemented_device_in Peter Maydell
2022-06-23 18:32 ` Peter Delevoryas
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=faba2fe7-0296-2e76-9f20-e41e159f359d@kaod.org \
--to=clg@kaod.org \
--cc="i.mitsyanko@gmail.com.mst"@redhat.com \
--cc=andrew@aj.id.au \
--cc=ani@anisinha.ca \
--cc=berrange@redhat.com \
--cc=eduardo@habkost.net \
--cc=f4bug@amsat.org \
--cc=joel@jms.id.au \
--cc=kvm@vger.kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=pdel@fb.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).