From: Gustavo Romero <gromero@linux.vnet.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,
Gustavo Romero <gromero@linux.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH] KVM: PPC: Book3S HV: Treat unrecognized TM instructions as illegal
Date: Thu, 13 Feb 2020 20:49:00 -0300 [thread overview]
Message-ID: <7968cea9-da2d-d5f6-bcb7-8549ac6c1899@linux.vnet.ibm.com> (raw)
In-Reply-To: <20200213233148.GK22482@gate.crashing.org>
Hi Segher,
Thanks a lot for reviewing it.
On 02/13/2020 08:31 PM, Segher Boessenkool wrote:
<snip>
>> ---
>> arch/powerpc/kvm/book3s_hv_tm.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/powerpc/kvm/book3s_hv_tm.c b/arch/powerpc/kvm/book3s_hv_tm.c
>> index 0db937497169..d342a9e11298 100644
>> --- a/arch/powerpc/kvm/book3s_hv_tm.c
>> +++ b/arch/powerpc/kvm/book3s_hv_tm.c
>> @@ -3,6 +3,8 @@
>> * Copyright 2017 Paul Mackerras, IBM Corp. <paulus@au1.ibm.com>
>> */
>>
>> +#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
>> +
>> #include <linux/kvm_host.h>
>>
>> #include <asm/kvm_ppc.h>
>> @@ -208,6 +210,8 @@ int kvmhv_p9_tm_emulation(struct kvm_vcpu *vcpu)
>> }
>>
>> /* What should we do here? We didn't recognize the instruction */
>> - WARN_ON_ONCE(1);
>> + kvmppc_core_queue_program(vcpu, SRR1_PROGILL);
>> + pr_warn_ratelimited("Unrecognized TM-related instruction %#x for emulation", instr);
>> +
>> return RESUME_GUEST;
>> }
>
> Do we actually know it is TM-related here? Otherwise, looks good to me :-)
Correct, I understand it's only TM-related here, so I don't expect anything else to hit 0x1500.
Best regards,
Gustavo
next prev parent reply other threads:[~2020-02-13 23:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 15:15 [PATCH] KVM: PPC: Book3S HV: Treat unrecognized TM instructions as illegal Gustavo Romero
2020-02-13 23:31 ` Segher Boessenkool
2020-02-13 23:49 ` Gustavo Romero [this message]
2020-02-17 1:07 ` Michael Neuling
2020-02-17 5:57 ` Segher Boessenkool
2020-02-17 6:23 ` Michael Neuling
2020-02-17 7:37 ` Segher Boessenkool
2020-02-18 21:23 ` Gustavo Romero
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=7968cea9-da2d-d5f6-bcb7-8549ac6c1899@linux.vnet.ibm.com \
--to=gromero@linux.vnet.ibm.com \
--cc=gromero@linux.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=segher@kernel.crashing.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).