From: Satheesh Rajendran <redacted>
This patch adds new defconfig options for powerpc KVM guest
and guest.config with additional config symbols enabled,
which is to build kernel to boot without initramfs and can be used
as place holder for guest specific additional config symbols in future.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Signed-off-by: Satheesh Rajendran <redacted>
---
arch/powerpc/Makefile | 8 ++++++++
arch/powerpc/configs/guest.config | 14 ++++++++++++++
2 files changed, 22 insertions(+)
create mode 100644 arch/powerpc/configs/guest.config
Why a guest kernel needs to have XFS integrated in the core image? I am
wondering if it is a requirement from another CONFIG_ option.
If it is not a strict requirement from another config, I think we can keep it
as defined at ppc64_defconfig, which defines it as module (CONFIG_XFS_FS=m).
Thanks for this patch, very useful.
Breno
Why a guest kernel needs to have XFS integrated in the core image? I am
wondering if it is a requirement from another CONFIG_ option.
Idea is to have a working config which would boot guest without initramfs,
other FS(like EXT4) is already integrated in the core image,
thought this would be helpful for distributions, which default XFS as root disk.
Hope this should be fine?
If it is not a strict requirement from another config, I think we can keep it
as defined at ppc64_defconfig, which defines it as module (CONFIG_XFS_FS=m).
Thanks for this patch, very useful.
Why a guest kernel needs to have XFS integrated in the core image? I am
wondering if it is a requirement from another CONFIG_ option.
Idea is to have a working config which would boot guest without initramfs,
other FS(like EXT4) is already integrated in the core image,
thought this would be helpful for distributions, which default XFS as root disk.
Nice! That makes sense and it is a good idea.
Thanks!
Why a guest kernel needs to have XFS integrated in the core image? I am
wondering if it is a requirement from another CONFIG_ option.
Idea is to have a working config which would boot guest without initramfs,
other FS(like EXT4) is already integrated in the core image,
thought this would be helpful for distributions, which default XFS as root disk.
Maybe we should switch XFS_FS to Y in ppc64_defconfig ?
cheers
Why a guest kernel needs to have XFS integrated in the core image? I am
wondering if it is a requirement from another CONFIG_ option.
Idea is to have a working config which would boot guest without initramfs,
other FS(like EXT4) is already integrated in the core image,
thought this would be helpful for distributions, which default XFS as root disk.
Maybe we should switch XFS_FS to Y in ppc64_defconfig ?
Sure, makes sense, will send it for ppc64_defconfig instead.
Inaddition, Have few more symbols to be enabled for cgroups,
memhotplug,numa balancing.
I guess these symbols can also go to ppc64_defconfig itself?.
i.e,
CONFIG_CGROUP_SCHED=y
CONFIG_MEMCG=y
CONFIG_CGROUP_SCHED=y
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_CGROUP_PERF=y
CONFIG_MEMORY_HOTPLUG=y
CONFIG_MEMORY_HOTREMOVE=y
CONFIG_NUMA_BALANCING=y
Thanks!
-Satheesh.
Why a guest kernel needs to have XFS integrated in the core image? I am
wondering if it is a requirement from another CONFIG_ option.
Idea is to have a working config which would boot guest without initramfs,
other FS(like EXT4) is already integrated in the core image,
thought this would be helpful for distributions, which default XFS as root disk.
Maybe we should switch XFS_FS to Y in ppc64_defconfig ?
Sure, makes sense, will send it for ppc64_defconfig instead.
Inaddition, Have few more symbols to be enabled for cgroups,
memhotplug,numa balancing.
I guess these symbols can also go to ppc64_defconfig itself?.
i.e,
CONFIG_CGROUP_SCHED=y
CONFIG_MEMCG=y
CONFIG_CGROUP_SCHED=y
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_CGROUP_PERF=y
CONFIG_MEMORY_HOTPLUG=y
CONFIG_MEMORY_HOTREMOVE=y
CONFIG_NUMA_BALANCING=y
Yeah I don't see why not, they're probably more or less required by
modern distros.
cheers