From: pbonzini@redhat.com (Paolo Bonzini)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] KVM API documentation patches
Date: Wed, 10 Sep 2014 11:34:53 +0200 [thread overview]
Message-ID: <54101B3D.20000@redhat.com> (raw)
In-Reply-To: <1410280039-2823-1-git-send-email-alex.bennee@linaro.org>
Il 09/09/2014 18:27, Alex Benn?e ha scritto:
> Hi,
>
> I'm preparing to add ARM KVM GDB support and I went to read the API
> documentation and found it surprisingly mute on the subject ;-)
>
> The first patch documents the "new" KVM_SET_GUEST_DEBUG ioctl based on
> reviewing the code. I've included a long CC list of people who've
> actually done the various implementations who I hope can sanity check
> the write-up. The second is a trivial formatting fix for what looks
> like a minor merge trip-up.
>
> Alex Benn?e (2):
> KVM: document KVM_SET_GUEST_DEBUG api
> KVM: fix api documentation of KVM_GET_EMULATED_CPUID
>
> Documentation/virtual/kvm/api.txt | 184 +++++++++++++++++++++++---------------
> 1 file changed, 114 insertions(+), 70 deletions(-)
>
Thanks, applying both!
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Cc: peter.maydell@linaro.org, christoffer.dall@linaro.org,
jan.kiszka@siemens.com, dahi@linux.vnet.ibm.com,
r65777@freescale.com, marc.zyngier@arm.com, bp@suse.de
Subject: Re: [PATCH 0/2] KVM API documentation patches
Date: Wed, 10 Sep 2014 11:34:53 +0200 [thread overview]
Message-ID: <54101B3D.20000@redhat.com> (raw)
In-Reply-To: <1410280039-2823-1-git-send-email-alex.bennee@linaro.org>
Il 09/09/2014 18:27, Alex Bennée ha scritto:
> Hi,
>
> I'm preparing to add ARM KVM GDB support and I went to read the API
> documentation and found it surprisingly mute on the subject ;-)
>
> The first patch documents the "new" KVM_SET_GUEST_DEBUG ioctl based on
> reviewing the code. I've included a long CC list of people who've
> actually done the various implementations who I hope can sanity check
> the write-up. The second is a trivial formatting fix for what looks
> like a minor merge trip-up.
>
> Alex Bennée (2):
> KVM: document KVM_SET_GUEST_DEBUG api
> KVM: fix api documentation of KVM_GET_EMULATED_CPUID
>
> Documentation/virtual/kvm/api.txt | 184 +++++++++++++++++++++++---------------
> 1 file changed, 114 insertions(+), 70 deletions(-)
>
Thanks, applying both!
Paolo
next prev parent reply other threads:[~2014-09-10 9:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 16:27 [PATCH 0/2] KVM API documentation patches Alex Bennée
2014-09-09 16:27 ` Alex Bennée
2014-09-09 16:27 ` [PATCH 1/2] KVM: document KVM_SET_GUEST_DEBUG api Alex Bennée
2014-09-09 16:27 ` Alex Bennée
2014-09-09 16:27 ` Alex Bennée
2014-09-11 22:56 ` Christoffer Dall
2014-09-11 22:56 ` Christoffer Dall
2014-09-09 16:27 ` [PATCH 2/2] KVM: fix api documentation of KVM_GET_EMULATED_CPUID Alex Bennée
2014-09-09 16:27 ` Alex Bennée
2014-09-09 16:27 ` Alex Bennée
2014-09-09 19:11 ` Borislav Petkov
2014-09-09 19:11 ` Borislav Petkov
2014-09-10 9:34 ` Paolo Bonzini [this message]
2014-09-10 9:34 ` [PATCH 0/2] KVM API documentation patches Paolo Bonzini
2014-09-11 22:58 ` Christoffer Dall
2014-09-11 22:58 ` Christoffer Dall
2014-09-15 15:56 ` Alex Bennée
2014-09-15 15:56 ` Alex Bennée
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=54101B3D.20000@redhat.com \
--to=pbonzini@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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.