From: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Cc: rkrcmar@redhat.com, paulus@ozlabs.org, dja@axtens.net
Subject: Re: [PATCH] kvm: add kvm cap values to debugfs
Date: Thu, 20 Jun 2019 16:25:53 +1000 [thread overview]
Message-ID: <1561011953.4771.2.camel@gmail.com> (raw)
In-Reply-To: <8f6429ac-f6a5-bf24-59c5-a101b75bfd40@redhat.com>
On Tue, 2019-05-28 at 12:35 +0200, Paolo Bonzini wrote:
> On 28/05/19 10:35, Suraj Jitindar Singh wrote:
> > KVM capabilities are used to communicate the availability of
> > certain
> > capabilities to userspace.
> >
> > It might be nice to know these values without having to add debug
> > printing to the userspace tool consuming this data.
>
> Why not write a separate script that prints the capability values?
I agree that this makes more sense as a standalone userspace script.
Dropping this patch.
Thanks,
Suraj
>
> Paolo
prev parent reply other threads:[~2019-06-20 6:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 8:35 [PATCH] kvm: add kvm cap values to debugfs Suraj Jitindar Singh
2019-05-28 10:32 ` Christian Borntraeger
2019-05-28 10:35 ` Paolo Bonzini
2019-06-20 6:25 ` Suraj Jitindar Singh [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=1561011953.4771.2.camel@gmail.com \
--to=sjitindarsingh@gmail.com \
--cc=dja@axtens.net \
--cc=kvm@vger.kernel.org \
--cc=paulus@ozlabs.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;
as well as URLs for NNTP newsgroup(s).