<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Kconfig</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>61df71ee - kvm: move &quot;select IRQ_BYPASS_MANAGER&quot; to common code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#61df71ee</link>
        <description>kvm: move &quot;select IRQ_BYPASS_MANAGER&quot; to common codeCONFIG_IRQ_BYPASS_MANAGER is a dependency of the common code included byCONFIG_HAVE_KVM_IRQ_BYPASS.  There is no advantage in adding the corresponding&quot;select&quot; directive to each architecture.Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Thu, 11 Jan 2024 08:02:05 +0000</pubDate>
        <dc:creator>Paolo Bonzini &lt;pbonzini@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>caadf876 - KVM: introduce CONFIG_KVM_COMMON</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#caadf876</link>
        <description>KVM: introduce CONFIG_KVM_COMMONCONFIG_HAVE_KVM is currently used by some architectures to eitherenabled the KVM config proper, or to enable host-side code that isnot part of the KVM module.  However, CONFIG_KVM&apos;s &quot;select&quot; statementin virt/kvm/Kconfig corresponds to a third meaning, namely toenable common Kconfigs required by all architectures that supportKVM.These three meanings can be replaced respectively by anarchitecture-specific Kconfig, by IS_ENABLED(CONFIG_KVM), or bya new Kconfig symbol that is in turn selected by thearchitecture-specific &quot;config KVM&quot;.Start by introducing such a new Kconfig symbol, CONFIG_KVM_COMMON.Unlike CONFIG_HAVE_KVM, it is selected by CONFIG_KVM, not byarchitecture code, and it brings in all dependencies of commonKVM code.  In particular, INTERVAL_TREE was missing in loongarchand riscv, so that is another thing that is fixed.Fixes: 8132d887a702 (&quot;KVM: remove CONFIG_HAVE_KVM_EVENTFD&quot;, 2023-12-08)Reported-by: Randy Dunlap &lt;rdunlap@infradead.org&gt;Closes: https://lore.kernel.org/all/44907c6b-c5bd-4e4a-a921-e4d3825539d8@infradead.org/Reviewed-by: Andrew Jones &lt;ajones@ventanamicro.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Thu, 04 Jan 2024 16:15:07 +0000</pubDate>
        <dc:creator>Paolo Bonzini &lt;pbonzini@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>c5b31cc2 - KVM: remove CONFIG_HAVE_KVM_IRQFD</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#c5b31cc2</link>
        <description>KVM: remove CONFIG_HAVE_KVM_IRQFDAll platforms with a kernel irqchip have support for irqfd.  Unify thetwo configuration items so that userspace can expect to use irqfd toinject interrupts into the irqchip.Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Wed, 18 Oct 2023 16:07:32 +0000</pubDate>
        <dc:creator>Paolo Bonzini &lt;pbonzini@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>8132d887 - KVM: remove CONFIG_HAVE_KVM_EVENTFD</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#8132d887</link>
        <description>KVM: remove CONFIG_HAVE_KVM_EVENTFDvirt/kvm/eventfd.c is compiled unconditionally, meaning that the ioeventfdsmember of struct kvm is accessed unconditionally.  CONFIG_HAVE_KVM_EVENTFDtherefore must be defined for KVM common code to compile successfully,remove it.Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Wed, 18 Oct 2023 16:11:56 +0000</pubDate>
        <dc:creator>Paolo Bonzini &lt;pbonzini@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>f128cf8c - KVM: Convert KVM_ARCH_WANT_MMU_NOTIFIER to CONFIG_KVM_GENERIC_MMU_NOTIFIER</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#f128cf8c</link>
        <description>KVM: Convert KVM_ARCH_WANT_MMU_NOTIFIER to CONFIG_KVM_GENERIC_MMU_NOTIFIERConvert KVM_ARCH_WANT_MMU_NOTIFIER into a Kconfig and select it whereappropriate to effectively maintain existing behavior.  Using a properKconfig will simplify building more functionality on top of KVM&apos;smmu_notifier infrastructure.Add a forward declaration of kvm_gfn_range to kvm_types.h so thatincluding arch/powerpc/include/asm/kvm_ppc.h&apos;s with CONFIG_KVM=n doesn&apos;tgenerate warnings due to kvm_gfn_range being undeclared.  PPC defineshooks for PR vs. HV without guarding them via #ifdeffery, e.g.  bool (*unmap_gfn_range)(struct kvm *kvm, struct kvm_gfn_range *range);  bool (*age_gfn)(struct kvm *kvm, struct kvm_gfn_range *range);  bool (*test_age_gfn)(struct kvm *kvm, struct kvm_gfn_range *range);  bool (*set_spte_gfn)(struct kvm *kvm, struct kvm_gfn_range *range);Alternatively, PPC could forward declare kvm_gfn_range, but there&apos;s nogood reason not to define it in common KVM.Acked-by: Anup Patel &lt;anup@brainfault.org&gt;Signed-off-by: Sean Christopherson &lt;seanjc@google.com&gt;Reviewed-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;Reviewed-by: Fuad Tabba &lt;tabba@google.com&gt;Tested-by: Fuad Tabba &lt;tabba@google.com&gt;Message-Id: &lt;20231027182217.3615211-8-seanjc@google.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Fri, 27 Oct 2023 18:21:49 +0000</pubDate>
        <dc:creator>Sean Christopherson &lt;seanjc@google.com&gt;</dc:creator>
    </item>
<item>
        <title>79cf833b - kvm: Remove &quot;select SRCU&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#79cf833b</link>
        <description>kvm: Remove &quot;select SRCU&quot;Now that the SRCU Kconfig option is unconditionally selected, there isno longer any point in selecting it.  Therefore, remove the &quot;select SRCU&quot;Kconfig statements from the various KVM Kconfig files.Acked-by: Sean Christopherson &lt;seanjc@google.com&gt; (x86)Signed-off-by: Paul E. McKenney &lt;paulmck@kernel.org&gt;Cc: Huacai Chen &lt;chenhuacai@kernel.org&gt;Cc: Aleksandar Markovic &lt;aleksandar.qemu.devel@gmail.com&gt;Cc: Thomas Bogendoerfer &lt;tsbogend@alpha.franken.de&gt;Cc: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Cc: Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;Cc: Sean Christopherson &lt;seanjc@google.com&gt;Cc: Paolo Bonzini &lt;pbonzini@redhat.com&gt;Cc: Thomas Gleixner &lt;tglx@linutronix.de&gt;Cc: Ingo Molnar &lt;mingo@redhat.com&gt;Cc: Borislav Petkov &lt;bp@alien8.de&gt;Cc: Dave Hansen &lt;dave.hansen@linux.intel.com&gt;Cc: &quot;H. Peter Anvin&quot; &lt;hpa@zytor.com&gt;Cc: &lt;kvm@vger.kernel.org&gt;Acked-by: Marc Zyngier &lt;maz@kernel.org&gt; (arm64)Acked-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt; (powerpc)Acked-by: Anup Patel &lt;anup@brainfault.org&gt; (riscv)Acked-by: Heiko Carstens &lt;hca@linux.ibm.com&gt; (s390)Reviewed-by: John Ogness &lt;john.ogness@linutronix.de&gt;Signed-off-by: Joel Fernandes (Google) &lt;joel@joelfernandes.org&gt;

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Fri, 24 Mar 2023 20:52:47 +0000</pubDate>
        <dc:creator>Paul E. McKenney &lt;paulmck@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>e59b3399 - KVM: PPC: BookS PR-KVM and BookE do not support context tracking</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#e59b3399</link>
        <description>KVM: PPC: BookS PR-KVM and BookE do not support context trackingThe context tracking code in PR-KVM and BookE implementations is notcomplete, and can cause host crashes if context tracking is enabled.Make these implementations depend on !CONTEXT_TRACKING_USER.Signed-off-by: Nicholas Piggin &lt;npiggin@gmail.com&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/20221014030729.2077151-2-npiggin@gmail.com

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Fri, 14 Oct 2022 03:07:28 +0000</pubDate>
        <dc:creator>Nicholas Piggin &lt;npiggin@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>688de017 - powerpc: Change CONFIG_E500 to CONFIG_PPC_E500</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#688de017</link>
        <description>powerpc: Change CONFIG_E500 to CONFIG_PPC_E500It will be used outside arch/powerpc, make it clear its apowerpc configuration item.And we already have CONFIG_PPC_E500MC, so that will makeit more consistent.Signed-off-by: Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/e63b22083c11c4300f4a82d3123a46e5fdd54fa6.1663606876.git.christophe.leroy@csgroup.eu

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Mon, 19 Sep 2022 17:01:35 +0000</pubDate>
        <dc:creator>Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;</dc:creator>
    </item>
<item>
        <title>81e9685d - KVM: PPC: Kconfig: Fix indentation</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#81e9685d</link>
        <description>KVM: PPC: Kconfig: Fix indentationThe convention for indentation seems to be a single tab. Help text isfurther indented by an additional two whitespaces. Fix the lines thatviolate these rules.Signed-off-by: Juerg Haefliger &lt;juergh@canonical.com&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/20220520115431.147593-1-juergh@canonical.com

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Fri, 20 May 2022 11:54:31 +0000</pubDate>
        <dc:creator>Juerg Haefliger &lt;juerg.haefliger@canonical.com&gt;</dc:creator>
    </item>
<item>
        <title>b44bb1b7 - KVM: PPC: Book3S HV: Provide more detailed timings for P9 entry path</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#b44bb1b7</link>
        <description>KVM: PPC: Book3S HV: Provide more detailed timings for P9 entry pathAlter the data collection points for the debug timing code in the P9path to be more in line with what the code does. The points where weaccumulate time are now the following:vcpu_entry: From vcpu_run_hv entry until the start of the inner loop;guest_entry: From the start of the inner loop until the guest entry in             asm;in_guest: From the guest entry in asm until the return to KVM C code;guest_exit: From the return into KVM C code until the corresponding            hypercall/page fault handling or re-entry into the guest;hypercall: Time spent handling hcalls in the kernel (hcalls can go to	   QEMU, not accounted here);page_fault: Time spent handling page faults;vcpu_exit: vcpu_run_hv exit (almost no code here currently).Like before, these are exposed in debugfs in a file called&quot;timings&quot;. There are four values:- number of occurrences of the accumulation point;- total time the vcpu spent in the phase in ns;- shortest time the vcpu spent in the phase in ns;- longest time the vcpu spent in the phase in ns;===Before:  rm_entry: 53132 16793518 256 4060  rm_intr: 53132 2125914 22 340  rm_exit: 53132 24108344 374 2180  guest: 53132 40980507996 404 9997650  cede: 0 0 0 0After:  vcpu_entry: 34637 7716108 178 4416  guest_entry: 52414 49365608 324 747542  in_guest: 52411 40828715840 258 9997480  guest_exit: 52410 19681717182 826 102496674  vcpu_exit: 34636 1744462 38 182  hypercall: 45712 22878288 38 1307962  page_fault: 992 111104034 568 168688  With just one instruction (hcall):  vcpu_entry: 1 942 942 942  guest_entry: 1 4044 4044 4044  in_guest: 1 1540 1540 1540  guest_exit: 1 3542 3542 3542  vcpu_exit: 1 80 80 80  hypercall: 0 0 0 0  page_fault: 0 0 0 0===Signed-off-by: Fabiano Rosas &lt;farosas@linux.ibm.com&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/20220525130554.2614394-6-farosas@linux.ibm.com

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Wed, 25 May 2022 13:05:54 +0000</pubDate>
        <dc:creator>Fabiano Rosas &lt;farosas@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>c3fa64c9 - KVM: PPC: Book3S HV: Decouple the debug timing from the P8 entry path</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#c3fa64c9</link>
        <description>KVM: PPC: Book3S HV: Decouple the debug timing from the P8 entry pathWe are currently doing the timing for debug purposes of the P9 entrypath using the accumulators and terminology defined by the old entrypath for P8 machines.Not only the &quot;real-mode&quot; and &quot;napping&quot; mentions are out of place forthe P9 Radix entry path but also we cannot change them because thetiming code is coupled to the structures defined in structkvm_vcpu_arch.Add a new CONFIG_KVM_BOOK3S_HV_P9_TIMING to enable the timing code forthe P9 entry path. For now, just add the new CONFIG and duplicate thestructures. A subsequent patch will add the P9 changes.Signed-off-by: Fabiano Rosas &lt;farosas@linux.ibm.com&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/20220525130554.2614394-4-farosas@linux.ibm.com

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Wed, 25 May 2022 13:05:52 +0000</pubDate>
        <dc:creator>Fabiano Rosas &lt;farosas@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>3f8ed993 - KVM: PPC: Book3S HV: Add a new config for P8 debug timing</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#3f8ed993</link>
        <description>KVM: PPC: Book3S HV: Add a new config for P8 debug timingTurn the existing Kconfig KVM_BOOK3S_HV_EXIT_TIMING intoKVM_BOOK3S_HV_P8_TIMING in preparation for the addition of a newconfig for P9 timings.This applies only to P8 code, the generic timing code is still keptunder KVM_BOOK3S_HV_EXIT_TIMING.Signed-off-by: Fabiano Rosas &lt;farosas@linux.ibm.com&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/20220525130554.2614394-3-farosas@linux.ibm.com

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Wed, 25 May 2022 13:05:51 +0000</pubDate>
        <dc:creator>Fabiano Rosas &lt;farosas@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>b5149e22 - KVM: PPC: Book3S PR: Disable SCV when AIL could be disabled</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#b5149e22</link>
        <description>KVM: PPC: Book3S PR: Disable SCV when AIL could be disabledPR KVM does not support running with AIL enabled, and SCV does is notsupported with AIL disabled. Fix this by ensuring the SCV facility isdisabled with FSCR while a CPU could be running with AIL=0.The PowerNV host supports disabling AIL on a per-CPU basis, so SCV justneeds to be disabled when a vCPU is being run.The pSeries machine can only switch AIL on a system-wide basis, so itmust disable SCV support at boot if the configuration can potentiallyrun a PR KVM guest.Also ensure a the FSCR[SCV] bit can not be enabled when emulatingmtFSCR for the guest.SCV is not emulated for the PR guest at the moment, this just fixes thehost crashes.Alternatives considered and rejected:- SCV support can not be disabled by PR KVM after boot, because it is  advertised to userspace with HWCAP.- AIL can not be disabled on a per-CPU basis. At least when running on  pseries it is a per-LPAR setting.- Support for real-mode SCV vectors will not be added because they are  at 0x17000 so making such a large fixed head space causes immediate  value limits to be exceeded, requiring a lot rework and more code.- Disabling SCV for any PR KVM possible kernel will cause a slowdown  when not using PR KVM.- A boot time option to disable SCV to use PR KVM is user-hostile.- System call instruction emulation for SCV facility unavailable  instructions is too complex and old emulation code was subtly broken  and removed.Signed-off-by: Nicholas Piggin &lt;npiggin@gmail.com&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Reviewed-by: Fabiano Rosas &lt;farosas@linux.ibm.com&gt;Link: https://lore.kernel.org/r/20220222064727.2314380-2-npiggin@gmail.com

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Tue, 22 Feb 2022 06:47:25 +0000</pubDate>
        <dc:creator>Nicholas Piggin &lt;npiggin@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>c2857374 - powerpc/64s: Make hash MMU support configurable</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#c2857374</link>
        <description>powerpc/64s: Make hash MMU support configurableThis adds Kconfig selection which allows 64s hash MMU support to bedisabled. It can be disabled if radix support is enabled, the minimumsupported CPU type is POWER9 (or higher), and KVM is not selected.Signed-off-by: Nicholas Piggin &lt;npiggin@gmail.com&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/20211201144153.2456614-17-npiggin@gmail.com

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Wed, 01 Dec 2021 14:41:51 +0000</pubDate>
        <dc:creator>Nicholas Piggin &lt;npiggin@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>ed922739 - KVM: Use interval tree to do fast hva lookup in memslots</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#ed922739</link>
        <description>KVM: Use interval tree to do fast hva lookup in memslotsThe current memslots implementation only allows quick binary search by gfn,quick lookup by hva is not possible - the implementation has to do a linearscan of the whole memslots array, even though the operation being performedmight apply just to a single memslot.This significantly hurts performance of per-hva operations with highermemslot counts.Since hva ranges can overlap between memslots an interval tree is neededfor tracking them.[sean: handle interval tree updates in kvm_replace_memslot()]Signed-off-by: Maciej S. Szmigiero &lt;maciej.szmigiero@oracle.com&gt;Message-Id: &lt;d66b9974becaa9839be9c4e1a5de97b177b4ac20.1638817640.git.maciej.szmigiero@oracle.com&gt;

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Mon, 06 Dec 2021 19:54:28 +0000</pubDate>
        <dc:creator>Maciej S. Szmigiero &lt;maciej.szmigiero@oracle.com&gt;</dc:creator>
    </item>
<item>
        <title>d3c8a2d3 - KVM: PPC: Book3S HV: Don&apos;t always save PMU for guest capable of nesting</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#d3c8a2d3</link>
        <description>KVM: PPC: Book3S HV: Don&apos;t always save PMU for guest capable of nestingProvide a config option that controls the workaround added by commit63279eeb7f93 (&quot;KVM: PPC: Book3S HV: Always save guest pmu for guestcapable of nesting&quot;). The option defaults to y for now, but is expectedto go away within a few releases.Nested capable guests running with the earlier commit 178266389794(&quot;KVM: PPC: Book3S HV Nested: Reflect guest PMU in-use to L0 when guestSPRs are live&quot;) will now indicate the PMU in-use status of their guests,which means the parent does not need to unconditionally save the PMU fornested capable guests.After this latest round of performance optimisations, this option costsabout 540 cycles or 10% entry/exit performance on a POWER9 nested-capableguest.Signed-off-by: Nicholas Piggin &lt;npiggin@gmail.com&gt;Reviewed-by: Fabiano Rosas &lt;farosas@linux.ibm.com&gt;References: 178266389794 (&quot;KVM: PPC: Book3S HV Nested: Reflect guest PMU in-use to L0 when guest SPRs are live&quot;)Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/20211123095231.1036501-11-npiggin@gmail.com

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Tue, 23 Nov 2021 09:51:48 +0000</pubDate>
        <dc:creator>Nicholas Piggin &lt;npiggin@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>c26d4c5d - powerpc/kvm: Remove obsolete and unneeded select</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#c26d4c5d</link>
        <description>powerpc/kvm: Remove obsolete and unneeded selectCommit a278e7ea608b (&quot;powerpc: Fix compile issue with force DAWR&quot;)selects the non-existing config PPC_DAWR_FORCE_ENABLE for configKVM_BOOK3S_64_HANDLER. As this commit also introduces a config PPC_DAWRand this config PPC_DAWR is selected with PPC if PPC64, there is noneed for any further select in the KVM_BOOK3S_64_HANDLER.Remove an obsolete and unneeded select in config KVM_BOOK3S_64_HANDLER.The issue was identified with ./scripts/checkkconfigsymbols.py.Fixes: a278e7ea608b (&quot;powerpc: Fix compile issue with force DAWR&quot;)Signed-off-by: Lukas Bulwahn &lt;lukas.bulwahn@gmail.com&gt;Reviewed-by: Daniel Axtens &lt;dja@axtens.net&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/20210819113954.17515-2-lukas.bulwahn@gmail.com

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Thu, 19 Aug 2021 11:39:53 +0000</pubDate>
        <dc:creator>Lukas Bulwahn &lt;lukas.bulwahn@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>27f69957 - powerpc/kvm: Force selection of CONFIG_PPC_FPU</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#27f69957</link>
        <description>powerpc/kvm: Force selection of CONFIG_PPC_FPUbook3s/32 kvm is designed with the assumption thatan FPU is always present.Force selection of FPU support in the kernel whenbuild KVM.Fixes: 7d68c8916950 (&quot;powerpc/32s: Allow deselecting CONFIG_PPC_FPU on mpc832x&quot;)Reported-by: kernel test robot &lt;lkp@intel.com&gt;Signed-off-by: Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/74461a99fa1466f361532ca794ca0753be3d9f86.1611038044.git.christophe.leroy@csgroup.eu

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Tue, 19 Jan 2021 06:36:52 +0000</pubDate>
        <dc:creator>Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;</dc:creator>
    </item>
<item>
        <title>a7f7f624 - treewide: replace &apos;---help---&apos; in Kconfig files with &apos;help&apos;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#a7f7f624</link>
        <description>treewide: replace &apos;---help---&apos; in Kconfig files with &apos;help&apos;Since commit 84af7a6194e4 (&quot;checkpatch: kconfig: prefer &apos;help&apos; over&apos;---help---&apos;&quot;), the number of &apos;---help---&apos; has been graduallydecreasing, but there are still more than 2400 instances.This commit finishes the conversion. While I touched the lines,I also fixed the indentation.There are a variety of indentation styles found.  a) 4 spaces + &apos;---help---&apos;  b) 7 spaces + &apos;---help---&apos;  c) 8 spaces + &apos;---help---&apos;  d) 1 space + 1 tab + &apos;---help---&apos;  e) 1 tab + &apos;---help---&apos;    (correct indentation)  f) 1 tab + 1 space + &apos;---help---&apos;  g) 1 tab + 2 spaces + &apos;---help---&apos;In order to convert all of them to 1 tab + &apos;help&apos;, I ran thefollowing commend:  $ find . -name &apos;Kconfig*&apos; | xargs sed -i &apos;s/^[[:space:]]*---help---/\thelp/&apos;Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Sat, 13 Jun 2020 16:50:22 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>20c384f1 - vhost: refine vhost and vringh kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kvm/Kconfig#20c384f1</link>
        <description>vhost: refine vhost and vringh kconfigCurrently, CONFIG_VHOST depends on CONFIG_VIRTUALIZATION. But vhost isnot necessarily for VM since it&apos;s a generic userspace and kernelcommunication protocol. Such dependency may prevent archs withoutvirtualization support from using vhost.To solve this, a dedicated vhost menu is created under drivers soCONIFG_VHOST can be decoupled out of CONFIG_VIRTUALIZATION.While at it, also squash Kconfig.vringh into vhost Kconfig file. Thisavoids the trick of conditional inclusion from VOP or CAIF. Then itwill be easier to introduce new vringh users and common dependency forboth vringh and vhost.Signed-off-by: Jason Wang &lt;jasowang@redhat.com&gt;Link: https://lore.kernel.org/r/20200326140125.19794-2-jasowang@redhat.comSigned-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;

            List of files:
            /linux-6.15/arch/powerpc/kvm/Kconfig</description>
        <pubDate>Thu, 26 Mar 2020 14:01:17 +0000</pubDate>
        <dc:creator>Jason Wang &lt;jasowang@redhat.com&gt;</dc:creator>
    </item>
</channel>
</rss>
