qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alistair Francis <alistair23@gmail.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, Weiwei Li <liweiwei@iscas.ac.cn>,
	 Richard Henderson <richard.henderson@linaro.org>,
	 Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
	qemu-riscv@nongnu.org,
	 Alistair Francis <alistair.francis@wdc.com>,
	Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Bin Meng <bin.meng@windriver.com>
Subject: Re: [PATCH v2] target/riscv: Restrict KVM-specific fields from ArchCPU
Date: Mon, 3 Jul 2023 11:41:29 +1000	[thread overview]
Message-ID: <CAKmqyKOR_f_Kh2fJ3ArgruS+bgfkBe=m8aMm4-r3z_bDKGwTbw@mail.gmail.com> (raw)
In-Reply-To: <20230624192957.14067-1-philmd@linaro.org>

On Sun, Jun 25, 2023 at 5:30 AM Philippe Mathieu-Daudé
<philmd@linaro.org> wrote:
>
> These fields shouldn't be accessed when KVM is not available.
>
> Restrict the KVM timer migration state. Rename the KVM timer
> post_load() handler accordingly, because cpu_post_load() is
> too generic.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>

Reviewed-by: Alistair Francis <alistair.francis@wdc.com>

Alistair

> ---
> Since v1 https://lore.kernel.org/qemu-devel/20230405160454.97436-10-philmd@linaro.org/:
> - Restrict whole vmstate_kvmtimer (thus drop Daniel's R-b)
> ---
>  target/riscv/cpu.h     | 2 ++
>  target/riscv/machine.c | 8 ++++++--
>  2 files changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/target/riscv/cpu.h b/target/riscv/cpu.h
> index e3e08d315f..b1b56aa29e 100644
> --- a/target/riscv/cpu.h
> +++ b/target/riscv/cpu.h
> @@ -363,12 +363,14 @@ struct CPUArchState {
>      hwaddr kernel_addr;
>      hwaddr fdt_addr;
>
> +#ifdef CONFIG_KVM
>      /* kvm timer */
>      bool kvm_timer_dirty;
>      uint64_t kvm_timer_time;
>      uint64_t kvm_timer_compare;
>      uint64_t kvm_timer_state;
>      uint64_t kvm_timer_frequency;
> +#endif /* CONFIG_KVM */
>  };
>
>  /*
> diff --git a/target/riscv/machine.c b/target/riscv/machine.c
> index 3ce2970785..d27f8a2a3a 100644
> --- a/target/riscv/machine.c
> +++ b/target/riscv/machine.c
> @@ -199,7 +199,8 @@ static bool kvmtimer_needed(void *opaque)
>      return kvm_enabled();
>  }
>
> -static int cpu_post_load(void *opaque, int version_id)
> +#ifdef CONFIG_KVM
> +static int cpu_kvmtimer_post_load(void *opaque, int version_id)
>  {
>      RISCVCPU *cpu = opaque;
>      CPURISCVState *env = &cpu->env;
> @@ -213,7 +214,7 @@ static const VMStateDescription vmstate_kvmtimer = {
>      .version_id = 1,
>      .minimum_version_id = 1,
>      .needed = kvmtimer_needed,
> -    .post_load = cpu_post_load,
> +    .post_load = cpu_kvmtimer_post_load,
>      .fields = (VMStateField[]) {
>          VMSTATE_UINT64(env.kvm_timer_time, RISCVCPU),
>          VMSTATE_UINT64(env.kvm_timer_compare, RISCVCPU),
> @@ -221,6 +222,7 @@ static const VMStateDescription vmstate_kvmtimer = {
>          VMSTATE_END_OF_LIST()
>      }
>  };
> +#endif
>
>  static bool debug_needed(void *opaque)
>  {
> @@ -409,7 +411,9 @@ const VMStateDescription vmstate_riscv_cpu = {
>          &vmstate_vector,
>          &vmstate_pointermasking,
>          &vmstate_rv128,
> +#ifdef CONFIG_KVM
>          &vmstate_kvmtimer,
> +#endif
>          &vmstate_envcfg,
>          &vmstate_debug,
>          &vmstate_smstateen,
> --
> 2.38.1
>
>


      parent reply	other threads:[~2023-07-03  1:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24 19:29 [PATCH v2] target/riscv: Restrict KVM-specific fields from ArchCPU Philippe Mathieu-Daudé
2023-06-25 23:27 ` Daniel Henrique Barboza
2023-06-26 10:56 ` Philippe Mathieu-Daudé
2023-07-03  1:41 ` Alistair Francis [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='CAKmqyKOR_f_Kh2fJ3ArgruS+bgfkBe=m8aMm4-r3z_bDKGwTbw@mail.gmail.com' \
    --to=alistair23@gmail.com \
    --cc=alistair.francis@wdc.com \
    --cc=bin.meng@windriver.com \
    --cc=dbarboza@ventanamicro.com \
    --cc=liweiwei@iscas.ac.cn \
    --cc=palmer@dabbelt.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --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 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).