From: Jonathan Corbet <corbet@lwn.net>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
rkrcmar@redhat.com, jdike@addtoit.com, richard@nod.at,
anton.ivanov@cambridgegreys.com, linux-doc@vger.kernel.org,
kvm@vger.kernel.org, linux-um@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: move Documentation/virtual to Documentation/virt
Date: Mon, 29 Jul 2019 07:55:54 -0600 [thread overview]
Message-ID: <20190729075554.46dfaaeb@lwn.net> (raw)
In-Reply-To: <be4ba4a7-a21b-8c56-4517-8886a754ff55@redhat.com>
On Sat, 27 Jul 2019 00:10:32 +0200
Paolo Bonzini <pbonzini@redhat.com> wrote:
> Does the userspace API
> cover only syscall or perhaps sysfs interfaces? There are more API
> files (amd-memory-encryption.txt, cpuid.txt, halt-polling.txt msr.txt,
> ppc-pv.txt, s390-diag.txt) but, with the exception of
> amd-memory-encryption.txt and halt-polling.txt, they cover the
> emulated-hardware interfaces that KVM provides to virtual machines.
The user-space API certainly goes beyond system calls. For sysfs, I
guess, the question would be whether a given knob is something that an
application would use (userspace-api) or something that a sysadmin would
want to tweak (admin-guide).
Thanks,
jon
prev parent reply other threads:[~2019-07-29 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 7:24 [PATCH] Documentation: move Documentation/virtual to Documentation/virt Christoph Hellwig
2019-07-24 8:51 ` Paolo Bonzini
2019-07-24 18:00 ` Jonathan Corbet
2019-07-26 22:10 ` Paolo Bonzini
2019-07-29 13:55 ` Jonathan Corbet [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=20190729075554.46dfaaeb@lwn.net \
--to=corbet@lwn.net \
--cc=anton.ivanov@cambridgegreys.com \
--cc=hch@lst.de \
--cc=jdike@addtoit.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=pbonzini@redhat.com \
--cc=richard@nod.at \
--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).