From: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
To: Greg Kurz <groug@kaod.org>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, David Gibson <david@gibson.dropbear.id.au>,
Alexey Kardashevskiy <aik@ozlabs.ru>
Subject: Re: [Qemu-devel] [PATCH] spapr: add missing break in h_get_cpu_characteristics()
Date: Fri, 02 Feb 2018 15:31:30 +1100 [thread overview]
Message-ID: <1517545890.2332.23.camel@gmail.com> (raw)
In-Reply-To: <151751446151.11348.15065690714406381610.stgit@bahia.lan>
On Thu, 2018-02-01 at 20:47 +0100, Greg Kurz wrote:
> Detected by Coverity (CID 1385702). This fixes the recently added
> hypercall
> to let guests properly apply Spectre and Meltdown workarounds.
>
> Fixes: c59704b25473 "target/ppc/spapr: Add H-Call
> H_GET_CPU_CHARACTERISTICS"
> Signed-off-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
> ---
> hw/ppc/spapr_hcall.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/ppc/spapr_hcall.c b/hw/ppc/spapr_hcall.c
> index 4d0e6eb0cf1d..596f58378a40 100644
> --- a/hw/ppc/spapr_hcall.c
> +++ b/hw/ppc/spapr_hcall.c
> @@ -1697,6 +1697,7 @@ static target_ulong
> h_get_cpu_characteristics(PowerPCCPU *cpu,
> switch (safe_indirect_branch) {
> case SPAPR_CAP_FIXED:
> characteristics |= H_CPU_CHAR_BCCTRL_SERIALISED;
> + break;
> default: /* broken */
> assert(safe_indirect_branch == SPAPR_CAP_BROKEN);
> break;
>
next prev parent reply other threads:[~2018-02-02 4:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 19:47 [Qemu-devel] [PATCH] spapr: add missing break in h_get_cpu_characteristics() Greg Kurz
2018-02-02 4:31 ` Suraj Jitindar Singh [this message]
2018-02-02 9:11 ` [Qemu-devel] [Qemu-ppc] " Daniel Henrique Barboza
2018-02-02 10:00 ` Greg Kurz
2018-02-02 11:18 ` Daniel Henrique Barboza
2018-02-08 23:28 ` [Qemu-devel] " David Gibson
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=1517545890.2332.23.camel@gmail.com \
--to=sjitindarsingh@gmail.com \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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.