public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@linux•ibm.com>
To: kvm-ppc@vger•kernel.org
Cc: kvm@vger•kernel.org, rkrcmar@redhat•com, aik@ozlabs•ru,
	pbonzini@redhat•com, linuxppc-dev@lists•ozlabs.org,
	david@gibson•dropbear.id.au
Subject: [RFC PATCH 0/1] KVM: PPC: Inform userspace about singlestep support
Date: Wed, 20 Mar 2019 15:39:49 -0300	[thread overview]
Message-ID: <20190320183951.29537-1-farosas@linux.ibm.com> (raw)

I am looking for a way to inform userspace about the lack of an
implementation in KVM HV for single stepping of instructions
(KVM_GUESTDGB_SINGLESTEP bit from SET_GUEST_DEBUG ioctl).

This will be used by QEMU to decide whether to attempt a call to the
set_guest_debug ioctl (for BookE, KVM PR) or fallback to a QEMU only
implementation (for KVM HV).

QEMU thread:
http://patchwork.ozlabs.org/cover/1049811/

My current proposal is to introduce a ppc-specific capability for
this. However I'm not sure if this would be better as a cap common for
all architectures or even if it should report on all of the possible
set_guest_debug flags to cover for the future.

Please comment. Thanks.


Fabiano Rosas (1):
  KVM: PPC: Report single stepping capability

 arch/powerpc/kvm/powerpc.c | 5 +++++
 include/uapi/linux/kvm.h   | 1 +
 2 files changed, 6 insertions(+)

--
2.20.1


             reply	other threads:[~2019-03-20 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-20 18:39 Fabiano Rosas [this message]
2019-03-20 18:39 ` [RFC PATCH 1/1] KVM: PPC: Report single stepping capability Fabiano Rosas
2019-03-21  4:44   ` Alexey Kardashevskiy
2019-03-21 14:35     ` Fabiano Rosas
2019-04-24  4:14   ` Paul Mackerras

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=20190320183951.29537-1-farosas@linux.ibm.com \
    --to=farosas@linux$(echo .)ibm.com \
    --cc=aik@ozlabs$(echo .)ru \
    --cc=david@gibson$(echo .)dropbear.id.au \
    --cc=kvm-ppc@vger$(echo .)kernel.org \
    --cc=kvm@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=pbonzini@redhat$(echo .)com \
    --cc=rkrcmar@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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