From: Stefan Fritsch <sf@sfritsch.de>
To: Jim Mattson <jmattson@google.com>, Paolo Bonzini <pbonzini@redhat.com>
Cc: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"the arch/x86 maintainers" <x86@kernel.org>,
"kvm list" <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kvm: Add emulation for movups/movupd
Date: Fri, 15 Jan 2021 09:56:53 +0100 [thread overview]
Message-ID: <884f1474-3654-95c4-9a57-338d28e65b38@sfritsch.de> (raw)
In-Reply-To: <CALMp9eR0OjUV7LsWQ_r4o20wSZ0dw0eGs=LJ0htLmwwvcuUP_A@mail.gmail.com>
Am 13.01.21 um 00:47 schrieb Jim Mattson:
> On Wed, Apr 4, 2018 at 10:44 PM Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>> On 04/04/2018 19:35, Stefan Fritsch wrote:
>>> On Wednesday, 4 April 2018 19:24:20 CEST Paolo Bonzini wrote:
>>>> On 04/04/2018 19:10, Konrad Rzeszutek Wilk wrote:
>>>>> Should there be a corresponding test-case?
>>>>
>>>> Good point! Stefan, could you write one?
>>>
>>> Is there infrastructure for such tests? If yes, can you give me a pointer to
>>> it?
>>
>> Yes, check out x86/emulator.c in
>> https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git. There is
>> already a movaps test.
>
> Whatever became of this unit test? I don't see it in the
> kvm-unit-tests repository.
>
Sorry, I did not get around to doing this. And it is unlikely that I
will have time to do it in the near future.
Cheers,
Stefan
next prev parent reply other threads:[~2021-01-15 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 15:54 [PATCH] kvm: Add emulation for movups/movupd Stefan Fritsch
2018-04-03 19:44 ` Radim Krčmář
2018-04-04 15:53 ` Paolo Bonzini
2018-04-04 17:10 ` Konrad Rzeszutek Wilk
2018-04-04 17:24 ` Paolo Bonzini
2018-04-04 17:35 ` Stefan Fritsch
2018-04-05 5:44 ` Paolo Bonzini
2021-01-12 23:47 ` Jim Mattson
2021-01-15 8:56 ` Stefan Fritsch [this message]
2018-04-05 1:33 ` Sasha Levin
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=884f1474-3654-95c4-9a57-338d28e65b38@sfritsch.de \
--to=sf@sfritsch.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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.