From: Cornelia Huck <cohuck@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, rkrcmar@redhat.com
Subject: Re: [PATCH] Documentation: kvm: fix dirty log ioctl arch lists
Date: Mon, 29 Apr 2019 10:49:07 +0200 [thread overview]
Message-ID: <20190429104907.17bf2824.cohuck@redhat.com> (raw)
In-Reply-To: <20190429082710.15570-1-drjones@redhat.com>
On Mon, 29 Apr 2019 10:27:10 +0200
Andrew Jones <drjones@redhat.com> wrote:
> KVM_GET_DIRTY_LOG is implemented by all architectures, not just x86,
> and KVM_CAP_MANUAL_DIRTY_LOG_PROTECT is additionally implemented by
> arm, arm64, and mips.
>
> Signed-off-by: Andrew Jones <drjones@redhat.com>
> ---
> I skimmed all ioctls in the document to see if others needed to be
> fixed, but from my quick skim the only dirty ones seem to be the
> dirty log ones.
>
> Documentation/virtual/kvm/api.txt | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2019-04-29 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 8:27 [PATCH] Documentation: kvm: fix dirty log ioctl arch lists Andrew Jones
2019-04-29 8:49 ` Cornelia Huck [this message]
2019-04-29 12:06 ` Paolo Bonzini
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=20190429104907.17bf2824.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@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