Commit 2f5947df authored by Christoph Hellwig's avatar Christoph Hellwig Committed by Paolo Bonzini

Documentation: move Documentation/virtual to Documentation/virt

Renaming docs seems to be en vogue at the moment, so fix on of the
grossly misnamed directories.  We usually never use "virtual" as
a shortcut for virtualization in the kernel, but always virt,
as seen in the virt/ top-level directory.  Fix up the documentation
to match that.

Fixes: ed16648e ("Move kvm, uml, and lguest subdirectories under a common "virtual" directory, I.E:")
Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
parent c6bf2ae9
...@@ -2532,7 +2532,7 @@ ...@@ -2532,7 +2532,7 @@
mem_encrypt=on: Activate SME mem_encrypt=on: Activate SME
mem_encrypt=off: Do not activate SME mem_encrypt=off: Do not activate SME
Refer to Documentation/virtual/kvm/amd-memory-encryption.rst Refer to Documentation/virt/kvm/amd-memory-encryption.rst
for details on when memory encryption can be activated. for details on when memory encryption can be activated.
mem_sleep_default= [SUSPEND] Default system suspend mode: mem_sleep_default= [SUSPEND] Default system suspend mode:
......
...@@ -3781,7 +3781,7 @@ encrypted VMs. ...@@ -3781,7 +3781,7 @@ encrypted VMs.
Currently, this ioctl is used for issuing Secure Encrypted Virtualization Currently, this ioctl is used for issuing Secure Encrypted Virtualization
(SEV) commands on AMD Processors. The SEV commands are defined in (SEV) commands on AMD Processors. The SEV commands are defined in
Documentation/virtual/kvm/amd-memory-encryption.rst. Documentation/virt/kvm/amd-memory-encryption.rst.
4.111 KVM_MEMORY_ENCRYPT_REG_REGION 4.111 KVM_MEMORY_ENCRYPT_REG_REGION
......
...@@ -18,7 +18,7 @@ S390: ...@@ -18,7 +18,7 @@ S390:
number in R1. number in R1.
For further information on the S390 diagnose call as supported by KVM, For further information on the S390 diagnose call as supported by KVM,
refer to Documentation/virtual/kvm/s390-diag.txt. refer to Documentation/virt/kvm/s390-diag.txt.
PowerPC: PowerPC:
It uses R3-R10 and hypercall number in R11. R4-R11 are used as output registers. It uses R3-R10 and hypercall number in R11. R4-R11 are used as output registers.
...@@ -26,7 +26,7 @@ S390: ...@@ -26,7 +26,7 @@ S390:
KVM hypercalls uses 4 byte opcode, that are patched with 'hypercall-instructions' KVM hypercalls uses 4 byte opcode, that are patched with 'hypercall-instructions'
property inside the device tree's /hypervisor node. property inside the device tree's /hypervisor node.
For more information refer to Documentation/virtual/kvm/ppc-pv.txt For more information refer to Documentation/virt/kvm/ppc-pv.txt
MIPS: MIPS:
KVM hypercalls use the HYPCALL instruction with code 0 and the hypercall KVM hypercalls use the HYPCALL instruction with code 0 and the hypercall
......
...@@ -298,7 +298,7 @@ Handling a page fault is performed as follows: ...@@ -298,7 +298,7 @@ Handling a page fault is performed as follows:
vcpu->arch.mmio_gfn, and call the emulator vcpu->arch.mmio_gfn, and call the emulator
- If both P bit and R/W bit of error code are set, this could possibly - If both P bit and R/W bit of error code are set, this could possibly
be handled as a "fast page fault" (fixed without taking the MMU lock). See be handled as a "fast page fault" (fixed without taking the MMU lock). See
the description in Documentation/virtual/kvm/locking.txt. the description in Documentation/virt/kvm/locking.txt.
- if needed, walk the guest page tables to determine the guest translation - if needed, walk the guest page tables to determine the guest translation
(gva->gpa or ngpa->gpa) (gva->gpa or ngpa->gpa)
- if permissions are insufficient, reflect the fault back to the guest - if permissions are insufficient, reflect the fault back to the guest
......
...@@ -7,7 +7,7 @@ Review checklist for kvm patches ...@@ -7,7 +7,7 @@ Review checklist for kvm patches
2. Patches should be against kvm.git master branch. 2. Patches should be against kvm.git master branch.
3. If the patch introduces or modifies a new userspace API: 3. If the patch introduces or modifies a new userspace API:
- the API must be documented in Documentation/virtual/kvm/api.txt - the API must be documented in Documentation/virt/kvm/api.txt
- the API must be discoverable using KVM_CHECK_EXTENSION - the API must be discoverable using KVM_CHECK_EXTENSION
4. New state must include support for save/restore. 4. New state must include support for save/restore.
......
...@@ -8727,7 +8727,7 @@ L: kvm@vger.kernel.org ...@@ -8727,7 +8727,7 @@ L: kvm@vger.kernel.org
W: http://www.linux-kvm.org W: http://www.linux-kvm.org
T: git git://git.kernel.org/pub/scm/virt/kvm/kvm.git T: git git://git.kernel.org/pub/scm/virt/kvm/kvm.git
S: Supported S: Supported
F: Documentation/virtual/kvm/ F: Documentation/virt/kvm/
F: include/trace/events/kvm.h F: include/trace/events/kvm.h
F: include/uapi/asm-generic/kvm* F: include/uapi/asm-generic/kvm*
F: include/uapi/linux/kvm* F: include/uapi/linux/kvm*
...@@ -12054,7 +12054,7 @@ M: Juergen Gross <jgross@suse.com> ...@@ -12054,7 +12054,7 @@ M: Juergen Gross <jgross@suse.com>
M: Alok Kataria <akataria@vmware.com> M: Alok Kataria <akataria@vmware.com>
L: virtualization@lists.linux-foundation.org L: virtualization@lists.linux-foundation.org
S: Supported S: Supported
F: Documentation/virtual/paravirt_ops.txt F: Documentation/virt/paravirt_ops.txt
F: arch/*/kernel/paravirt* F: arch/*/kernel/paravirt*
F: arch/*/include/asm/paravirt*.h F: arch/*/include/asm/paravirt*.h
F: include/linux/hypervisor.h F: include/linux/hypervisor.h
...@@ -16745,7 +16745,7 @@ W: http://user-mode-linux.sourceforge.net ...@@ -16745,7 +16745,7 @@ W: http://user-mode-linux.sourceforge.net
Q: https://patchwork.ozlabs.org/project/linux-um/list/ Q: https://patchwork.ozlabs.org/project/linux-um/list/
T: git git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git T: git git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git
S: Maintained S: Maintained
F: Documentation/virtual/uml/ F: Documentation/virt/uml/
F: arch/um/ F: arch/um/
F: arch/x86/um/ F: arch/x86/um/
F: fs/hostfs/ F: fs/hostfs/
......
...@@ -31,7 +31,7 @@ ...@@ -31,7 +31,7 @@
* Struct fields are always 32 or 64 bit aligned, depending on them being 32 * Struct fields are always 32 or 64 bit aligned, depending on them being 32
* or 64 bit wide respectively. * or 64 bit wide respectively.
* *
* See Documentation/virtual/kvm/ppc-pv.txt * See Documentation/virt/kvm/ppc-pv.txt
*/ */
struct kvm_vcpu_arch_shared { struct kvm_vcpu_arch_shared {
__u64 scratch1; __u64 scratch1;
......
...@@ -3466,7 +3466,7 @@ static bool fast_page_fault(struct kvm_vcpu *vcpu, gva_t gva, int level, ...@@ -3466,7 +3466,7 @@ static bool fast_page_fault(struct kvm_vcpu *vcpu, gva_t gva, int level,
/* /*
* Currently, fast page fault only works for direct mapping * Currently, fast page fault only works for direct mapping
* since the gfn is not stable for indirect shadow page. See * since the gfn is not stable for indirect shadow page. See
* Documentation/virtual/kvm/locking.txt to get more detail. * Documentation/virt/kvm/locking.txt to get more detail.
*/ */
fault_handled = fast_pf_fix_direct_spte(vcpu, sp, fault_handled = fast_pf_fix_direct_spte(vcpu, sp,
iterator.sptep, spte, iterator.sptep, spte,
......
...@@ -116,7 +116,7 @@ struct kvm_irq_level { ...@@ -116,7 +116,7 @@ struct kvm_irq_level {
* ACPI gsi notion of irq. * ACPI gsi notion of irq.
* For IA-64 (APIC model) IOAPIC0: irq 0-23; IOAPIC1: irq 24-47.. * For IA-64 (APIC model) IOAPIC0: irq 0-23; IOAPIC1: irq 24-47..
* For X86 (standard AT mode) PIC0/1: irq 0-15. IOAPIC0: 0-23.. * For X86 (standard AT mode) PIC0/1: irq 0-15. IOAPIC0: 0-23..
* For ARM: See Documentation/virtual/kvm/api.txt * For ARM: See Documentation/virt/kvm/api.txt
*/ */
union { union {
__u32 irq; __u32 irq;
...@@ -1086,7 +1086,7 @@ struct kvm_xen_hvm_config { ...@@ -1086,7 +1086,7 @@ struct kvm_xen_hvm_config {
* *
* KVM_IRQFD_FLAG_RESAMPLE indicates resamplefd is valid and specifies * KVM_IRQFD_FLAG_RESAMPLE indicates resamplefd is valid and specifies
* the irqfd to operate in resampling mode for level triggered interrupt * the irqfd to operate in resampling mode for level triggered interrupt
* emulation. See Documentation/virtual/kvm/api.txt. * emulation. See Documentation/virt/kvm/api.txt.
*/ */
#define KVM_IRQFD_FLAG_RESAMPLE (1 << 1) #define KVM_IRQFD_FLAG_RESAMPLE (1 << 1)
......
...@@ -116,7 +116,7 @@ struct kvm_irq_level { ...@@ -116,7 +116,7 @@ struct kvm_irq_level {
* ACPI gsi notion of irq. * ACPI gsi notion of irq.
* For IA-64 (APIC model) IOAPIC0: irq 0-23; IOAPIC1: irq 24-47.. * For IA-64 (APIC model) IOAPIC0: irq 0-23; IOAPIC1: irq 24-47..
* For X86 (standard AT mode) PIC0/1: irq 0-15. IOAPIC0: 0-23.. * For X86 (standard AT mode) PIC0/1: irq 0-15. IOAPIC0: 0-23..
* For ARM: See Documentation/virtual/kvm/api.txt * For ARM: See Documentation/virt/kvm/api.txt
*/ */
union { union {
__u32 irq; __u32 irq;
...@@ -1085,7 +1085,7 @@ struct kvm_xen_hvm_config { ...@@ -1085,7 +1085,7 @@ struct kvm_xen_hvm_config {
* *
* KVM_IRQFD_FLAG_RESAMPLE indicates resamplefd is valid and specifies * KVM_IRQFD_FLAG_RESAMPLE indicates resamplefd is valid and specifies
* the irqfd to operate in resampling mode for level triggered interrupt * the irqfd to operate in resampling mode for level triggered interrupt
* emulation. See Documentation/virtual/kvm/api.txt. * emulation. See Documentation/virt/kvm/api.txt.
*/ */
#define KVM_IRQFD_FLAG_RESAMPLE (1 << 1) #define KVM_IRQFD_FLAG_RESAMPLE (1 << 1)
......
...@@ -727,7 +727,7 @@ int kvm_arch_vcpu_ioctl_run(struct kvm_vcpu *vcpu, struct kvm_run *run) ...@@ -727,7 +727,7 @@ int kvm_arch_vcpu_ioctl_run(struct kvm_vcpu *vcpu, struct kvm_run *run)
* Ensure we set mode to IN_GUEST_MODE after we disable * Ensure we set mode to IN_GUEST_MODE after we disable
* interrupts and before the final VCPU requests check. * interrupts and before the final VCPU requests check.
* See the comment in kvm_vcpu_exiting_guest_mode() and * See the comment in kvm_vcpu_exiting_guest_mode() and
* Documentation/virtual/kvm/vcpu-requests.rst * Documentation/virt/kvm/vcpu-requests.rst
*/ */
smp_store_mb(vcpu->mode, IN_GUEST_MODE); smp_store_mb(vcpu->mode, IN_GUEST_MODE);
......
...@@ -250,7 +250,7 @@ static unsigned long vgic_v3_uaccess_read_pending(struct kvm_vcpu *vcpu, ...@@ -250,7 +250,7 @@ static unsigned long vgic_v3_uaccess_read_pending(struct kvm_vcpu *vcpu,
* pending state of interrupt is latched in pending_latch variable. * pending state of interrupt is latched in pending_latch variable.
* Userspace will save and restore pending state and line_level * Userspace will save and restore pending state and line_level
* separately. * separately.
* Refer to Documentation/virtual/kvm/devices/arm-vgic-v3.txt * Refer to Documentation/virt/kvm/devices/arm-vgic-v3.txt
* for handling of ISPENDR and ICPENDR. * for handling of ISPENDR and ICPENDR.
*/ */
for (i = 0; i < len * 8; i++) { for (i = 0; i < len * 8; i++) {
......
...@@ -42,7 +42,7 @@ ...@@ -42,7 +42,7 @@
VGIC_AFFINITY_LEVEL(val, 3)) VGIC_AFFINITY_LEVEL(val, 3))
/* /*
* As per Documentation/virtual/kvm/devices/arm-vgic-v3.txt, * As per Documentation/virt/kvm/devices/arm-vgic-v3.txt,
* below macros are defined for CPUREG encoding. * below macros are defined for CPUREG encoding.
*/ */
#define KVM_REG_ARM_VGIC_SYSREG_OP0_MASK 0x000000000000c000 #define KVM_REG_ARM_VGIC_SYSREG_OP0_MASK 0x000000000000c000
...@@ -63,7 +63,7 @@ ...@@ -63,7 +63,7 @@
KVM_REG_ARM_VGIC_SYSREG_OP2_MASK) KVM_REG_ARM_VGIC_SYSREG_OP2_MASK)
/* /*
* As per Documentation/virtual/kvm/devices/arm-vgic-its.txt, * As per Documentation/virt/kvm/devices/arm-vgic-its.txt,
* below macros are defined for ITS table entry encoding. * below macros are defined for ITS table entry encoding.
*/ */
#define KVM_ITS_CTE_VALID_SHIFT 63 #define KVM_ITS_CTE_VALID_SHIFT 63
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment