From: "Philippe Mathieu-Daudé" <f4bug@amsat.org> To: Eduardo Habkost <ehabkost@redhat.com>, Juan Quintela <quintela@redhat.com> Cc: "Peter Maydell" <peter.maydell@linaro.org>, "Sarah Harris" <S.E.Harris@kent.ac.uk>, "Cornelia Huck" <cohuck@redhat.com>, "Sagar Karandikar" <sagark@eecs.berkeley.edu>, "David Hildenbrand" <david@redhat.com>, "Anthony Green" <green@moxielogic.com>, "Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>, qemu-devel@nongnu.org, "Max Filippov" <jcmvbkbc@gmail.com>, "Taylor Simpson" <tsimpson@quicinc.com>, "Alistair Francis" <Alistair.Francis@wdc.com>, "Edgar E. Iglesias" <edgar.iglesias@gmail.com>, "Guan Xuetao" <gxt@mprc.pku.edu.cn>, "Marek Vasut" <marex@denx.de>, "Yoshinori Sato" <ysato@users.sourceforge.jp>, "Michael S. Tsirkin" <mst@redhat.com>, "Claudio Fontana" <cfontana@suse.de>, qemu-ppc@nongnu.org, "Philippe Mathieu-Daudé" <philmd@redhat.com>, "Artyom Tarasenko" <atar4qemu@gmail.com>, "Thomas Huth" <thuth@redhat.com>, "Richard Henderson" <richard.henderson@linaro.org>, "Greg Kurz" <groug@kaod.org>, qemu-s390x@nongnu.org, qemu-arm@nongnu.org, "Michael Rolnik" <mrolnik@gmail.com>, "Stafford Horne" <shorne@gmail.com>, "Alex Bennée" <alex.bennee@linaro.org>, "David Gibson" <david@gibson.dropbear.id.au>, qemu-riscv@nongnu.org, "Bastian Koppelmann" <kbastian@mail.uni-paderborn.de>, "Chris Wulff" <crwulff@gmail.com>, "Laurent Vivier" <laurent@vivier.eu>, "Michael Walle" <michael@walle.cc>, "Palmer Dabbelt" <palmer@dabbelt.com>, "Paolo Bonzini" <pbonzini@redhat.com>, "Aleksandar Rikalo" <aleksandar.rikalo@syrmia.com>, "Aurelien Jarno" <aurelien@aurel32.net> Subject: Re: [PATCH v3 01/27] target: Set CPUClass::vmsd instead of DeviceClass::vmsd Date: Thu, 22 Apr 2021 11:55:27 +0200 [thread overview] Message-ID: <cccb8e5c-55cb-3f46-1391-ca96ab7c27ce@amsat.org> (raw) In-Reply-To: <20210421220333.bkxo6zriqe6w3rim@habkost.net> +Juan On 4/22/21 12:03 AM, Eduardo Habkost wrote: > On Tue, Mar 02, 2021 at 03:57:52PM +0100, Philippe Mathieu-Daudé wrote: >> The cpu model is the single device available in user-mode. >> Since we want to restrict some fields to user-mode emulation, >> we prefer to set the vmsd field of CPUClass, rather than the >> DeviceClass one. >> >> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org> > > Is this going to have an externally visible effect? On system emulation, no, because unchanged. On user emulation migration it is not used, the symbol is here to satisfy linking: include/hw/core/cpu.h-1070-#ifdef CONFIG_SOFTMMU include/hw/core/cpu.h-1071-extern const VMStateDescription vmstate_cpu_common; include/hw/core/cpu.h-1072-#else include/hw/core/cpu.h:1073:#define vmstate_cpu_common vmstate_dummy include/hw/core/cpu.h-1074-#endif include/migration/vmstate.h:197:extern const VMStateDescription vmstate_dummy; stubs/vmstate.c:4:const VMStateDescription vmstate_dummy = {}; > If it does, how can we make sure it's safe? > > If it does not, do you know why CPUClass::vmsd exists in the > first place? My guess is CPUState is the only device used in user emulation, so it would be a way to restrict the vmstate_dummy to CPU and not to any DeviceState? But looking at the introductory commit: commit b170fce3dd06372f7bfec9a780ebcb1fce6d57e4 Author: Andreas Färber <afaerber@suse.de> Date: Sun Jan 20 20:23:22 2013 +0100 cpu: Register VMStateDescription through CPUState In comparison to DeviceClass::vmsd, CPU VMState is split in two, "cpu_common" and "cpu", and uses cpu_index as instance_id instead of -1. Therefore add a CPU-specific CPUClass::vmsd field. Unlike the legacy CPUArchState registration, rather register CPUState. Juan, do you remember? > > Do you think it would be simpler to just squash this patch into > [PATCH v3 08/27] cpu: Move CPUClass::vmsd to SysemuCPUOps > ? Certainly cleaner, I'll respin! Thanks, Phil.
WARNING: multiple messages have this Message-ID (diff)
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org> To: Eduardo Habkost <ehabkost@redhat.com>, Juan Quintela <quintela@redhat.com> Cc: qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>, "Sarah Harris" <S.E.Harris@kent.ac.uk>, "Chris Wulff" <crwulff@gmail.com>, "Sagar Karandikar" <sagark@eecs.berkeley.edu>, "David Hildenbrand" <david@redhat.com>, "Anthony Green" <green@moxielogic.com>, "Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>, "Aleksandar Rikalo" <aleksandar.rikalo@syrmia.com>, "Max Filippov" <jcmvbkbc@gmail.com>, "Taylor Simpson" <tsimpson@quicinc.com>, "Alistair Francis" <Alistair.Francis@wdc.com>, "Edgar E. Iglesias" <edgar.iglesias@gmail.com>, "Guan Xuetao" <gxt@mprc.pku.edu.cn>, "Marek Vasut" <marex@denx.de>, "Yoshinori Sato" <ysato@users.sourceforge.jp>, "Michael S. Tsirkin" <mst@redhat.com>, "Claudio Fontana" <cfontana@suse.de>, "Palmer Dabbelt" <palmer@dabbelt.com>, "Philippe Mathieu-Daudé" <philmd@redhat.com>, "Artyom Tarasenko" <atar4qemu@gmail.com>, "Thomas Huth" <thuth@redhat.com>, "Richard Henderson" <richard.henderson@linaro.org>, "Greg Kurz" <groug@kaod.org>, qemu-s390x@nongnu.org, qemu-arm@nongnu.org, "Michael Rolnik" <mrolnik@gmail.com>, "Stafford Horne" <shorne@gmail.com>, "Alex Bennée" <alex.bennee@linaro.org>, "David Gibson" <david@gibson.dropbear.id.au>, qemu-riscv@nongnu.org, "Bastian Koppelmann" <kbastian@mail.uni-paderborn.de>, "Cornelia Huck" <cohuck@redhat.com>, "Laurent Vivier" <laurent@vivier.eu>, "Michael Walle" <michael@walle.cc>, qemu-ppc@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>, "Aurelien Jarno" <aurelien@aurel32.net> Subject: Re: [PATCH v3 01/27] target: Set CPUClass::vmsd instead of DeviceClass::vmsd Date: Thu, 22 Apr 2021 11:55:27 +0200 [thread overview] Message-ID: <cccb8e5c-55cb-3f46-1391-ca96ab7c27ce@amsat.org> (raw) In-Reply-To: <20210421220333.bkxo6zriqe6w3rim@habkost.net> +Juan On 4/22/21 12:03 AM, Eduardo Habkost wrote: > On Tue, Mar 02, 2021 at 03:57:52PM +0100, Philippe Mathieu-Daudé wrote: >> The cpu model is the single device available in user-mode. >> Since we want to restrict some fields to user-mode emulation, >> we prefer to set the vmsd field of CPUClass, rather than the >> DeviceClass one. >> >> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org> > > Is this going to have an externally visible effect? On system emulation, no, because unchanged. On user emulation migration it is not used, the symbol is here to satisfy linking: include/hw/core/cpu.h-1070-#ifdef CONFIG_SOFTMMU include/hw/core/cpu.h-1071-extern const VMStateDescription vmstate_cpu_common; include/hw/core/cpu.h-1072-#else include/hw/core/cpu.h:1073:#define vmstate_cpu_common vmstate_dummy include/hw/core/cpu.h-1074-#endif include/migration/vmstate.h:197:extern const VMStateDescription vmstate_dummy; stubs/vmstate.c:4:const VMStateDescription vmstate_dummy = {}; > If it does, how can we make sure it's safe? > > If it does not, do you know why CPUClass::vmsd exists in the > first place? My guess is CPUState is the only device used in user emulation, so it would be a way to restrict the vmstate_dummy to CPU and not to any DeviceState? But looking at the introductory commit: commit b170fce3dd06372f7bfec9a780ebcb1fce6d57e4 Author: Andreas Färber <afaerber@suse.de> Date: Sun Jan 20 20:23:22 2013 +0100 cpu: Register VMStateDescription through CPUState In comparison to DeviceClass::vmsd, CPU VMState is split in two, "cpu_common" and "cpu", and uses cpu_index as instance_id instead of -1. Therefore add a CPU-specific CPUClass::vmsd field. Unlike the legacy CPUArchState registration, rather register CPUState. Juan, do you remember? > > Do you think it would be simpler to just squash this patch into > [PATCH v3 08/27] cpu: Move CPUClass::vmsd to SysemuCPUOps > ? Certainly cleaner, I'll respin! Thanks, Phil.
next prev parent reply other threads:[~2021-04-22 10:03 UTC|newest] Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-02 14:57 [PATCH v3 00/27] cpu: Introduce SysemuCPUOps structure, remove watchpoints from usermode Philippe Mathieu-Daudé 2021-03-02 14:57 ` Philippe Mathieu-Daudé 2021-03-02 14:57 ` [PATCH v3 01/27] target: Set CPUClass::vmsd instead of DeviceClass::vmsd Philippe Mathieu-Daudé 2021-03-02 14:57 ` Philippe Mathieu-Daudé 2021-04-21 22:03 ` Eduardo Habkost 2021-04-21 22:03 ` Eduardo Habkost 2021-04-22 9:55 ` Philippe Mathieu-Daudé [this message] 2021-04-22 9:55 ` Philippe Mathieu-Daudé 2021-04-22 10:28 ` Peter Maydell 2021-04-22 10:28 ` Peter Maydell 2021-04-22 11:01 ` Philippe Mathieu-Daudé 2021-04-22 11:01 ` Philippe Mathieu-Daudé 2021-04-22 15:41 ` Philippe Mathieu-Daudé 2021-04-22 15:41 ` Philippe Mathieu-Daudé 2021-04-22 15:53 ` Peter Maydell 2021-04-22 15:53 ` Peter Maydell 2021-04-22 16:05 ` Philippe Mathieu-Daudé 2021-04-22 16:05 ` Philippe Mathieu-Daudé 2021-03-02 14:57 ` [PATCH v3 02/27] cpu: Un-inline cpu_get_phys_page_debug and cpu_asidx_from_attrs Philippe Mathieu-Daudé 2021-03-02 14:57 ` Philippe Mathieu-Daudé 2021-03-02 14:57 ` [PATCH v3 03/27] cpu: Introduce cpu_virtio_is_big_endian() Philippe Mathieu-Daudé 2021-03-02 14:57 ` Philippe Mathieu-Daudé 2021-03-02 14:57 ` [PATCH v3 04/27] cpu: Directly use cpu_write_elf*() fallback handlers in place Philippe Mathieu-Daudé 2021-03-02 14:57 ` Philippe Mathieu-Daudé 2021-03-02 14:57 ` [PATCH v3 05/27] cpu: Directly use get_paging_enabled() " Philippe Mathieu-Daudé 2021-03-02 14:57 ` Philippe Mathieu-Daudé 2021-03-02 14:57 ` [PATCH v3 06/27] cpu: Directly use get_memory_mapping() " Philippe Mathieu-Daudé 2021-03-02 14:57 ` Philippe Mathieu-Daudé 2021-03-02 14:57 ` [PATCH v3 07/27] cpu: Introduce SysemuCPUOps structure Philippe Mathieu-Daudé 2021-03-02 14:57 ` Philippe Mathieu-Daudé 2021-03-03 5:18 ` Richard Henderson 2021-03-03 5:18 ` Richard Henderson 2021-03-02 14:57 ` [PATCH v3 08/27] cpu: Move CPUClass::vmsd to SysemuCPUOps Philippe Mathieu-Daudé 2021-03-02 14:57 ` Philippe Mathieu-Daudé 2021-03-02 14:58 ` [PATCH v3 09/27] cpu: Move CPUClass::virtio_is_big_endian " Philippe Mathieu-Daudé 2021-03-02 14:58 ` Philippe Mathieu-Daudé 2021-03-02 14:58 ` [PATCH v3 10/27] cpu: Move CPUClass::get_crash_info " Philippe Mathieu-Daudé 2021-03-02 14:58 ` Philippe Mathieu-Daudé 2021-03-02 14:58 ` [PATCH v3 11/27] cpu: Move CPUClass::write_elf* " Philippe Mathieu-Daudé 2021-03-02 14:58 ` Philippe Mathieu-Daudé 2021-03-02 14:58 ` [PATCH v3 12/27] cpu: Move CPUClass::asidx_from_attrs " Philippe Mathieu-Daudé 2021-03-02 14:58 ` Philippe Mathieu-Daudé 2021-03-02 14:58 ` [PATCH v3 13/27] cpu: Move CPUClass::get_phys_page_debug " Philippe Mathieu-Daudé 2021-03-02 14:58 ` Philippe Mathieu-Daudé 2021-03-02 14:58 ` [PATCH v3 14/27] cpu: Move CPUClass::get_memory_mapping " Philippe Mathieu-Daudé 2021-03-02 14:58 ` Philippe Mathieu-Daudé 2021-03-02 14:58 ` [PATCH v3 15/27] cpu: Move CPUClass::get_paging_enabled " Philippe Mathieu-Daudé 2021-03-02 14:58 ` Philippe Mathieu-Daudé 2021-03-02 14:58 ` [PATCH v3 16/27] cpu: Restrict "hw/core/sysemu-cpu-ops.h" to target/cpu.c Philippe Mathieu-Daudé 2021-03-02 14:58 ` Philippe Mathieu-Daudé 2021-03-02 14:58 ` [PATCH v3 17/27] linux-user: Remove dead code Philippe Mathieu-Daudé 2021-03-02 14:58 ` Philippe Mathieu-Daudé 2021-03-03 15:17 ` Laurent Vivier 2021-03-03 15:17 ` Laurent Vivier 2021-03-02 14:58 ` [PATCH v3 18/27] gdbstub: Remove watchpoint dead code in gdbserver_fork() Philippe Mathieu-Daudé 2021-03-02 14:58 ` Philippe Mathieu-Daudé
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=cccb8e5c-55cb-3f46-1391-ca96ab7c27ce@amsat.org \ --to=f4bug@amsat.org \ --cc=Alistair.Francis@wdc.com \ --cc=S.E.Harris@kent.ac.uk \ --cc=aleksandar.rikalo@syrmia.com \ --cc=alex.bennee@linaro.org \ --cc=atar4qemu@gmail.com \ --cc=aurelien@aurel32.net \ --cc=cfontana@suse.de \ --cc=cohuck@redhat.com \ --cc=crwulff@gmail.com \ --cc=david@gibson.dropbear.id.au \ --cc=david@redhat.com \ --cc=edgar.iglesias@gmail.com \ --cc=ehabkost@redhat.com \ --cc=green@moxielogic.com \ --cc=groug@kaod.org \ --cc=gxt@mprc.pku.edu.cn \ --cc=jcmvbkbc@gmail.com \ --cc=kbastian@mail.uni-paderborn.de \ --cc=laurent@vivier.eu \ --cc=marex@denx.de \ --cc=mark.cave-ayland@ilande.co.uk \ --cc=michael@walle.cc \ --cc=mrolnik@gmail.com \ --cc=mst@redhat.com \ --cc=palmer@dabbelt.com \ --cc=pbonzini@redhat.com \ --cc=peter.maydell@linaro.org \ --cc=philmd@redhat.com \ --cc=qemu-arm@nongnu.org \ --cc=qemu-devel@nongnu.org \ --cc=qemu-ppc@nongnu.org \ --cc=qemu-riscv@nongnu.org \ --cc=qemu-s390x@nongnu.org \ --cc=quintela@redhat.com \ --cc=richard.henderson@linaro.org \ --cc=sagark@eecs.berkeley.edu \ --cc=shorne@gmail.com \ --cc=thuth@redhat.com \ --cc=tsimpson@quicinc.com \ --cc=ysato@users.sourceforge.jp \ /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: linkBe 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.