search for: config_acpi_numa

...ONFIG_ACPI_POWER_METER=m CONFIG_ACPI_SYSFS_POWER=y CONFIG_ACPI_PROC_EVENT=y CONFIG_ACPI_AC=y CONFIG_ACPI_BATTERY=y CONFIG_ACPI_BUTTON=y CONFIG_ACPI_VIDEO=m CONFIG_ACPI_FAN=y CONFIG_ACPI_DOCK=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_HOTPLUG_CPU=y CONFIG_ACPI_PROCESSOR_AGGREGATOR=m CONFIG_ACPI_THERMAL=y CONFIG_ACPI_NUMA=y # CONFIG_ACPI_CUSTOM_DSDT is not set CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_PCI_SLOT=y CONFIG_ACPI_CONTAINER=y CONFIG_ACPI_HOTPLUG_MEMORY=y CONFIG_ACPI_HOTPLUG_MEMORY_AUTO_ONLINE=y CONFIG_ACPI_SBS=m CONFIG_ACPI_HED=y CONFIG_ACPI_APEI=y CONFIG_ACPI_APEI_GHES=y CONF...

..., section 2, all goes wrong! My ~/rpmbuild/BUILD directory is empty! No configs directory too. No ~/rpmbuild/BUILD/kernel-*/linux-*/ available, all configs files are in ~/rpmbuild/SOURCES Since this I try to modify ~/rpmbuild/SOURCES/config-x86-generic because it was the only file containing the CONFIG_ACPI_NUMA flag. No success, the build does not take account of my changes as the ~/rpmbuild/BUILD/kernel-2.6.32-573.22.1.el6/linux-2.6.32-573.22.1.el6.numa.x86_64/.config created file with: rpmbuild -bb --without xen --without debug --without debuginfo --target=x86_64 ./SPECS/kernel.spec says "# CON...

...lding CentOS-6 kernels (not quite ready for CentOS-7). You really have to dot the i's and cross the t's. If you miss a step or command in there, chances are it will fail. > Since this I try to modify ~/rpmbuild/SOURCES/config-x86-generic because > it was the only file containing the CONFIG_ACPI_NUMA flag. No success, the > build does not take account of my changes as the > ~/rpmbuild/BUILD/kernel-2.6.32-573.22.1.el6/linux-2.6.32-573.22.1.el6.numa.x86_64/.config > created file with: > rpmbuild -bb --without xen --without debug --without debuginfo > --target=x86_64 ./SPECS/kernel....

...SPINLOCK_H */ diff --git a/arch/arm64/kernel/Makefile b/arch/arm64/kernel/Makefile index fc6488660f64..b23cdae433a4 100644 --- a/arch/arm64/kernel/Makefile +++ b/arch/arm64/kernel/Makefile @@ -50,7 +50,7 @@ obj-$(CONFIG_ARMV8_DEPRECATED) += armv8_deprecated.o obj-$(CONFIG_ACPI) += acpi.o obj-$(CONFIG_ACPI_NUMA) += acpi_numa.o obj-$(CONFIG_ARM64_ACPI_PARKING_PROTOCOL) += acpi_parking_protocol.o -obj-$(CONFIG_PARAVIRT) += paravirt.o +obj-$(CONFIG_PARAVIRT) += paravirt.o paravirt-spinlocks.o obj-$(CONFIG_RANDOMIZE_BASE) += kaslr.o obj-$(CONFIG_HIBERNATION) += hibernate.o hibernate-asm.o obj-$(CO...

...t > quite ready for CentOS-7). You really have to dot the i's and cross the > t's. If you miss a step or command in there, chances are it will fail. > > >> Since this I try to modify ~/rpmbuild/SOURCES/config-x86-generic because >> it was the only file containing the CONFIG_ACPI_NUMA flag. No success, the >> build does not take account of my changes as the >> ~/rpmbuild/BUILD/kernel-2.6.32-573.22.1.el6/linux-2.6.32-573.22.1.el6.numa.x86_64/.config >> created file with: >> rpmbuild -bb --without xen --without debug --without debuginfo >> --target=x8...

I'm very confused on the right step to use to setup a modified kernel in centOS6. As a simple user, I've downloaded the latests sources (I'm runing an old kernel version) : rpm -i http://vault.centos.org/6.7/updates/Source/SPackages/kernel-2.6.32-573.22.1.el6.src.rpm in the spec file ~/rpmbuild/SPECS/kernel.spec I've set: %define buildid .numa Now I want to set

...head-2007-02-08/arch/x86_64/kernel/setup-xen.c 2007-02-08 17:09:47.000000000 +0100 @@ -681,7 +681,8 @@ void __init setup_arch(char **cmdline_p) init_memory_mapping(0, (end_pfn_map << PAGE_SHIFT)); - /* dmi_scan_machine(); */ + if (is_initial_xendomain()) + dmi_scan_machine(); #ifdef CONFIG_ACPI_NUMA /* @@ -1630,13 +1629,6 @@ struct seq_operations cpuinfo_op = { .show = show_cpuinfo, }; -static int __init run_dmi_scan(void) -{ - dmi_scan_machine(); - return 0; -} -core_initcall(run_dmi_scan); - #if defined(CONFIG_INPUT_PCSPKR) || defined(CONFIG_INPUT_PCSPKR_MODULE) #include <linux/p...

...--------------- > 3. Changes RFC v4 -> v1 > -------------------------------------------------------------------------- > > Only minor things changed, especially, nothing on the virtio side. > - "virtio-mem: Paravirtualized memory hotplug" > -- Fix compilation without CONFIG_ACPI_NUMA > -- Minor code simplifications > -- Better lockdep handling > -- Fix retry handling when getting a config update while processing work > - "virtio-mem: Paravirtualized memory hotunplug part 1" > - "virtio-mem: Paravirtualized memory hotunplug part 2" > -- Unpl...

...amp;vm->removal_lock, flags); + if (!vm->removing) + queue_work(system_freezable_wq, &vm->wq); + spin_unlock_irqrestore(&vm->removal_lock, flags); +} + +static int virtio_mem_translate_node_id(struct virtio_mem *vm, uint16_t node_id) +{ + int node = NUMA_NO_NODE; + +#if defined(CONFIG_ACPI_NUMA) + if (virtio_has_feature(vm->vdev, VIRTIO_MEM_F_ACPI_PXM)) + node = pxm_to_node(node_id); +#endif + return node; +} + +/* + * Test if a virtio-mem device overlaps with the given range. Can be called + * from (notifier) callbacks lockless. + */ +static bool virtio_mem_overlaps_range(struct virt...

...--------------------------------------------- 3. Changes RFC v4 -> v1 -------------------------------------------------------------------------- Only minor things changed, especially, nothing on the virtio side. - "virtio-mem: Paravirtualized memory hotplug" -- Fix compilation without CONFIG_ACPI_NUMA -- Minor code simplifications -- Better lockdep handling -- Fix retry handling when getting a config update while processing work - "virtio-mem: Paravirtualized memory hotunplug part 1" - "virtio-mem: Paravirtualized memory hotunplug part 2" -- Unplug memory from highest to lowe...

...--------------------------------------------- 3. Changes RFC v4 -> v1 -------------------------------------------------------------------------- Only minor things changed, especially, nothing on the virtio side. - "virtio-mem: Paravirtualized memory hotplug" -- Fix compilation without CONFIG_ACPI_NUMA -- Minor code simplifications -- Better lockdep handling -- Fix retry handling when getting a config update while processing work - "virtio-mem: Paravirtualized memory hotunplug part 1" - "virtio-mem: Paravirtualized memory hotunplug part 2" -- Unplug memory from highest to lowe...

This patch set aims to support the vcpu_is_preempted() functionality under KVM/arm64, which allowing the guest to obtain the VCPU is currently running or not. This will enhance lock performance on overcommitted hosts (more runnable VCPUs than physical CPUs in the system) as doing busy waits for preempted VCPUs will hurt system performance far worse than early yielding. We have observed some

From: Zengruan Ye <yezengruan at huawei.com> This patch set aims to support the vcpu_is_preempted() functionality under KVM/arm64, which allowing the guest to obtain the vcpu is currently running or not. This will enhance lock performance on overcommitted hosts (more runnable vcpus than physical cpus in the system) as doing busy waits for preempted vcpus will hurt system performance far

From: Zengruan Ye <yezengruan at huawei.com> This patch set aims to support the vcpu_is_preempted() functionality under KVM/arm64, which allowing the guest to obtain the vcpu is currently running or not. This will enhance lock performance on overcommitted hosts (more runnable vcpus than physical cpus in the system) as doing busy waits for preempted vcpus will hurt system performance far

This series is based on v5.7-rc4. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-v4 This is basically a resend of v3 [1], now based on v5.7-rc4 and restested. One patch was reshuffled and two ACKs I missed to add were added. The rebase did not require any modifications to patches. Details about virtio-mem can be found in the cover letter of v2 [2]. A

This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-v2 I now have acks for all !virtio-mem changes. I'll be happy to get review feedback, testing reports, etc. for the virtio-mem changes. If there are no further comments, I guess this is good to go as a v1 soon. The basic idea of virtio-mem is to provide a

This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-rfc-v4 The basic idea of virtio-mem is to provide a flexible, cross-architecture memory hot(un)plug solution that avoids many limitations imposed by existing technologies, architectures, and interfaces. More details can be found below and in linked material. This

This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-rfc-v4 The basic idea of virtio-mem is to provide a flexible, cross-architecture memory hot(un)plug solution that avoids many limitations imposed by existing technologies, architectures, and interfaces. More details can be found below and in linked material. This

This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-v3 Patch #1 - #10 where contained in v2 and only contain minor modifications (mostly smaller fixes). The remaining patches are new and contain smaller optimizations. Details about virtio-mem can be found in the cover letter of v2 [1]. A basic QEMU implementation was

This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-v3 Patch #1 - #10 where contained in v2 and only contain minor modifications (mostly smaller fixes). The remaining patches are new and contain smaller optimizations. Details about virtio-mem can be found in the cover letter of v2 [1]. A basic QEMU implementation was