From: Thomas Huth <thuth@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>,
kvm@vger.kernel.org, kvm-ppc@vger.kernel.org
Cc: drjones@redhat.com, dgibson@redhat.com, pbonzini@redhat.com
Subject: Re: [kvm-unit-tests PATCH 2/5] powerpc: add test to check invalid instruction trap
Date: Fri, 18 Mar 2016 10:12:19 +0000 [thread overview]
Message-ID: <56EBD483.3040404@redhat.com> (raw)
In-Reply-To: <56EBD381.3040109@redhat.com>
On 18.03.2016 11:08, Laurent Vivier wrote:
>
>
> On 18/03/2016 10:51, Thomas Huth wrote:
>> On 16.03.2016 16:13, Laurent Vivier wrote:
>>> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
>>> ---
>>> powerpc/Makefile.common | 5 ++++-
>>> powerpc/emulator.c | 46 ++++++++++++++++++++++++++++++++++++++++++++++
>>> powerpc/unittests.cfg | 3 +++
>>> 3 files changed, 53 insertions(+), 1 deletion(-)
>>> create mode 100644 powerpc/emulator.c
>>>
>>> diff --git a/powerpc/Makefile.common b/powerpc/Makefile.common
>>> index ab2caf6..257e3fb 100644
>>> --- a/powerpc/Makefile.common
>>> +++ b/powerpc/Makefile.common
>>> @@ -7,7 +7,8 @@
>>> tests-common = \
>>> $(TEST_DIR)/selftest.elf \
>>> $(TEST_DIR)/spapr_hcall.elf \
>>> - $(TEST_DIR)/rtas.elf
>>> + $(TEST_DIR)/rtas.elf \
>>> + $(TEST_DIR)/emulator.elf
>>>
>>> all: $(TEST_DIR)/boot_rom.bin test_cases
>>>
>>> @@ -70,3 +71,5 @@ $(TEST_DIR)/selftest.elf: $(cstart.o) $(reloc.o) $(TEST_DIR)/selftest.o
>>> $(TEST_DIR)/spapr_hcall.elf: $(cstart.o) $(reloc.o) $(TEST_DIR)/spapr_hcall.o
>>>
>>> $(TEST_DIR)/rtas.elf: $(cstart.o) $(reloc.o) $(TEST_DIR)/rtas.o
>>> +
>>> +$(TEST_DIR)/emulator.elf: $(cstart.o) $(reloc.o) $(TEST_DIR)/emulator.o
>>> diff --git a/powerpc/emulator.c b/powerpc/emulator.c
>>> new file mode 100644
>>> index 0000000..1215c4f
>>> --- /dev/null
>>> +++ b/powerpc/emulator.c
>>> @@ -0,0 +1,46 @@
>>> +/*
>>> + * Test some powerpc instructions
>>> + */
>>> +
>>> +#include <libcflat.h>
>>> +#include <asm/processor.h>
>>> +
>>> +static int volatile is_invalid;
>>> +
>>> +static void program_check_handler(struct pt_regs *regs, void *opaque)
>>> +{
>>> + int *data = opaque;
>>> +
>>> + printf("Detected invalid instruction 0x%016lx: %08x\n",
>>> + regs->nip, *(uint32_t*)regs->nip);
>>
>> Should the test always print this, or is this rather confusing for the
>> users? Then it should maybe be commented out by default, I think.
>
> In fact, it was really helpful to debug (for instance with kvm-pr), it's
> why I let it. But as I agree with you, I'll remove it.
You could also add a CLI option to this unit test, so that it e.g. only
printed when the test is started with a "-v" parameter or so?
Thomas
next prev parent reply other threads:[~2016-03-18 10:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 15:12 [kvm-unit-tests PATCH 0/5] Check emulation Laurent Vivier
2016-03-16 15:12 ` [kvm-unit-tests PATCH 1/5] powerpc: add exception handler Laurent Vivier
2016-03-18 3:59 ` David Gibson
2016-03-18 8:53 ` Laurent Vivier
2016-03-18 9:42 ` Thomas Huth
2016-03-16 15:13 ` [kvm-unit-tests PATCH 2/5] powerpc: add test to check invalid instruction trap Laurent Vivier
2016-03-18 9:51 ` Thomas Huth
2016-03-18 10:08 ` Laurent Vivier
2016-03-18 10:12 ` Thomas Huth [this message]
2016-03-16 15:13 ` [kvm-unit-tests PATCH 3/5] powerpc: check 64bit mode Laurent Vivier
2016-03-18 8:28 ` Thomas Huth
2016-03-18 8:38 ` Paul Mackerras
2016-03-18 8:41 ` Thomas Huth
2016-03-16 15:13 ` [kvm-unit-tests PATCH 4/5] powerpc: check lswx Laurent Vivier
2016-03-18 9:09 ` Thomas Huth
2016-03-18 10:01 ` Laurent Vivier
2016-03-18 10:06 ` Thomas Huth
2016-03-18 10:18 ` Laurent Vivier
2016-03-18 10:34 ` Thomas Huth
2016-03-16 15:13 ` [kvm-unit-tests PATCH 5/5] powerpc: Check lswx in little-endian mode Laurent Vivier
2016-03-18 9:54 ` Thomas Huth
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=56EBD483.3040404@redhat.com \
--to=thuth@redhat.com \
--cc=dgibson@redhat.com \
--cc=drjones@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.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