All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
	Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Sergio Lopez <slp@redhat.com>, Song Gao <gaosong@loongson.cn>,
	Bibo Mao <maobibo@loongson.cn>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Alistair Francis <alistair.francis@wdc.com>,
	Weiwei Li <liwei1518@gmail.com>,
	Daniel Henrique Barboza <daniel.barboza@oss.qualcomm.com>,
	Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
	Chao Liu <chao.liu.zevorn@gmail.com>
Subject: Re: [PATCH 0/5] hw/nvram/fw_cfg: Document and tighten up register layouts
Date: Fri, 3 Jul 2026 06:23:49 -0400	[thread overview]
Message-ID: <20260703062108-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAFEAcA9GDPyd19-fdoepJesSbw=eZfPtPDTsa++yZ1F=j3p87Q@mail.gmail.com>

On Fri, Jul 03, 2026 at 10:41:32AM +0100, Peter Maydell wrote:
> These have all now been reviewed. Since fw_cfg is marked as
> Orphaned in MAINTAINERS,

I don't think fw cfg is good as orphaned.
Any takers? If not I guess I will have to add myself there.

> I'm going to take the series via
> target-arm.next. Let me know if anybody would prefer something else.
> 
> thanks
> -- PMM

Pls go ahead:
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>


> On Fri, 29 May 2026 at 18:46, Peter Maydell <peter.maydell@linaro.org> wrote:
> >
> > We support the fw_cfg device on more architectures and machines that
> > we let on about in the documentation.  Luckily most of the new ones
> > (notably riscv and loongarch) have followed the straightforward layout
> > that the Arm virt board picked. Allowing every machine type to have
> > its own special-snowflake register layout has no particular benefits
> > and tends to result in guest OSes accumulating ifdef ladders to deal
> > with all the unnecessary variation.
> >
> > This patchset:
> >  * updates the docs to present the arm/riscv/loongarch memory
> >    mapped layout as the "standard" layout to be used by all
> >    new architectures/machines in future
> >  * adds the layouts used by various existing boards that we
> >    didn't document (PA-RISC, SPARC, PPC and MIPS)
> >  * tightens up fw_cfg_init_mem_dma() and fw_cfg_init_io_dma()
> >    functions so that they don't provide flexibility to the
> >    caller to pick their own weird new layout. None of the
> >    callers were using this flexibility, so it's better to
> >    have fw_cfg_init_mem_dma() give the "standard MMIO" layout
> >    and fw_cfg_init_io_dma() give the x86 ioport layout.
> >
> > thanks
> > -- PMM
> >
> > Peter Maydell (5):
> >   docs/specs/fw_cfg: Document all architecture register layouts
> >   hw/nvram/fw_cfg: Enforce standard layout for fw_cfg_init_mem_dma()
> >   hw/nvram/fw_cfg: Enforce standard layout for x86 fw_cfg I/O ports
> >   hw/nvram/fw_cfg: Remove support for I/O port fw_cfg without DMA
> >   hw/nvram/fw_cfg: Document fw_cfg_init_mem_nodma()
> >
> >  docs/specs/fw_cfg.rst     | 28 ++++++++++++++++---
> >  hw/arm/virt.c             |  2 +-
> >  hw/i386/fw_cfg.c          |  3 +-
> >  hw/i386/microvm.c         |  3 +-
> >  hw/i386/pc.c              |  3 +-
> >  hw/loongarch/fw_cfg.c     |  3 +-
> >  hw/nvram/fw_cfg.c         | 22 ++++++---------
> >  hw/riscv/virt.c           |  3 +-
> >  include/hw/nvram/fw_cfg.h | 58 +++++++++++++++++++++++++++++++++++----
> >  9 files changed, 92 insertions(+), 33 deletions(-)



      reply	other threads:[~2026-07-03 10:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 17:46 [PATCH 0/5] hw/nvram/fw_cfg: Document and tighten up register layouts Peter Maydell
2026-05-29 17:46 ` [PATCH 1/5] docs/specs/fw_cfg: Document all architecture " Peter Maydell
2026-06-03  7:03   ` Philippe Mathieu-Daudé
2026-06-16  9:29     ` Peter Maydell
2026-06-24 17:24       ` Philippe Mathieu-Daudé
2026-05-29 17:46 ` [PATCH 2/5] hw/nvram/fw_cfg: Enforce standard layout for fw_cfg_init_mem_dma() Peter Maydell
2026-06-24 17:26   ` Philippe Mathieu-Daudé
2026-05-29 17:46 ` [PATCH 3/5] hw/nvram/fw_cfg: Enforce standard layout for x86 fw_cfg I/O ports Peter Maydell
2026-06-03  6:52   ` Philippe Mathieu-Daudé
2026-06-08  9:12     ` Peter Maydell
2026-06-08 16:02       ` Philippe Mathieu-Daudé
2026-06-08 16:11         ` Peter Maydell
2026-06-08 16:15           ` Philippe Mathieu-Daudé
2026-05-29 17:46 ` [PATCH 4/5] hw/nvram/fw_cfg: Remove support for I/O port fw_cfg without DMA Peter Maydell
2026-06-24 17:27   ` Philippe Mathieu-Daudé
2026-05-29 17:46 ` [PATCH 5/5] hw/nvram/fw_cfg: Document fw_cfg_init_mem_nodma() Peter Maydell
2026-06-03  6:48   ` Philippe Mathieu-Daudé
2026-05-29 20:26 ` [PATCH 0/5] hw/nvram/fw_cfg: Document and tighten up register layouts Richard Henderson
2026-07-03  9:41 ` Peter Maydell
2026-07-03 10:23   ` Michael S. Tsirkin [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=20260703062108-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=alistair.francis@wdc.com \
    --cc=chao.liu.zevorn@gmail.com \
    --cc=daniel.barboza@oss.qualcomm.com \
    --cc=gaosong@loongson.cn \
    --cc=jiaxun.yang@flygoat.com \
    --cc=kraxel@redhat.com \
    --cc=liwei1518@gmail.com \
    --cc=maobibo@loongson.cn \
    --cc=palmer@dabbelt.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=pierrick.bouvier@oss.qualcomm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=slp@redhat.com \
    --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 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.