From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH kvm-unit-tests v2 0/4] x86: hyperv_stimer: test direct mode
Date: Mon, 19 Apr 2021 17:41:08 +0200 [thread overview]
Message-ID: <87zgxui8ob.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20210224163547.197100-1-vkuznets@redhat.com>
Vitaly Kuznetsov <vkuznets@redhat.com> writes:
> Changes since v1:
> - Minor cosmetic changes. v1 was sent in October, 2019 and I completely
> forgot about it. Time to dust it off!
Ping) Patches should still apply to 'master' with no issues.
>
> Original description:
>
> Testing 'direct' mode requires us to add 'hv_stimer_direct' CPU flag to
> QEMU, create a new entry in unittests.cfg to not lose the ability to test
> stimers in 'VMbus message' mode.
>
> Vitaly Kuznetsov (4):
> x86: hyperv_stimer: keep SINT number parameter in 'struct stimer'
> x86: hyperv_stimer: define union hv_stimer_config
> x86: hyperv_stimer: don't require hyperv-testdev
> x86: hyperv_stimer: add direct mode tests
>
> x86/hyperv.h | 29 ++++++--
> x86/hyperv_stimer.c | 159 +++++++++++++++++++++++++++++++++++---------
> x86/unittests.cfg | 8 ++-
> 3 files changed, 157 insertions(+), 39 deletions(-)
--
Vitaly
prev parent reply other threads:[~2021-04-19 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 16:35 [PATCH kvm-unit-tests v2 0/4] x86: hyperv_stimer: test direct mode Vitaly Kuznetsov
2021-02-24 16:35 ` [PATCH kvm-unit-tests v2 1/4] x86: hyperv_stimer: keep SINT number parameter in 'struct stimer' Vitaly Kuznetsov
2021-02-24 16:35 ` [PATCH kvm-unit-tests v2 2/4] x86: hyperv_stimer: define union hv_stimer_config Vitaly Kuznetsov
2021-02-24 16:35 ` [PATCH kvm-unit-tests v2 3/4] x86: hyperv_stimer: don't require hyperv-testdev Vitaly Kuznetsov
2021-02-24 16:35 ` [PATCH kvm-unit-tests v2 4/4] x86: hyperv_stimer: add direct mode tests Vitaly Kuznetsov
2021-04-19 15:41 ` Vitaly Kuznetsov [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=87zgxui8ob.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=kvm@vger.kernel.org \
--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 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.