From: Paolo Bonzini <pbonzini@redhat.com>
To: Jonathan Corbet <corbet@lwn.net>
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: Sat, 27 Jul 2019 00:10:32 +0200 [thread overview]
Message-ID: <be4ba4a7-a21b-8c56-4517-8886a754ff55@redhat.com> (raw)
In-Reply-To: <20190724120005.31a990af@lwn.net>
On 24/07/19 20:00, Jonathan Corbet wrote:
> - kvm/api.txt pretty clearly belongs in the userspace-api book, rather
> than tossed in with:
>
> - kvm/review-checklist.txt, which belongs in the subsystem guide, if only
> we'd gotten around to creating it yet, or
>
> - kvm/mmu.txt, which is information for kernel developers, or
>
> - uml/UserModeLinux-HOWTO.txt, which belongs in the admin guide.
>
> I suspect that organization is going to be one of the main issues to talk
> about in Lisbon. Meanwhile, I hope that this rename won't preclude
> organizational work in the future.
Absolutely not, this rename was just about a badly-named directory. I
totally agree with the above reorganization. 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.
Paolo
next prev parent reply other threads:[~2019-07-26 22:10 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 [this message]
2019-07-29 13:55 ` Jonathan Corbet
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=be4ba4a7-a21b-8c56-4517-8886a754ff55@redhat.com \
--to=pbonzini@redhat.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=corbet@lwn.net \
--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=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).