diff for duplicates of <ZLrDopLH+3vN8rE6@google.com> diff --git a/a/1.txt b/N1/1.txt index 1680cf1..a8914e0 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -3,17 +3,17 @@ On Fri, Jul 21, 2023, Xiaoyao Li wrote: > > On 7/19/2023 7:44 AM, Sean Christopherson wrote: > > > @@ -6255,12 +6298,17 @@ int kvm_init(unsigned vcpu_size, unsigned > > > vcpu_align, struct module *module) -> > > ????? if (r) -> > > ????????? goto err_async_pf; -> > > +??? r = kvm_gmem_init(); -> > > +??? if (r) -> > > +??????? goto err_gmem; +> > > if (r) +> > > goto err_async_pf; +> > > + r = kvm_gmem_init(); +> > > + if (r) +> > > + goto err_gmem; > > > + -> > > ????? kvm_chardev_ops.owner = module; -> > > ????? kvm_preempt_ops.sched_in = kvm_sched_in; -> > > ????? kvm_preempt_ops.sched_out = kvm_sched_out; -> > > ????? kvm_init_debug(); -> > > +??? kvm_gmem_init(); +> > > kvm_chardev_ops.owner = module; +> > > kvm_preempt_ops.sched_in = kvm_sched_in; +> > > kvm_preempt_ops.sched_out = kvm_sched_out; +> > > kvm_init_debug(); +> > > + kvm_gmem_init(); > > > > why kvm_gmem_init() needs to be called again? by mistake? > diff --git a/a/content_digest b/N1/content_digest index bbe2fb8..5d3b557 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,9 +3,49 @@ "ref\0fdc155f5-041b-a1b1-15aa-8f970180a13a@intel.com\0" "ref\029baac45-7736-a28c-3b2d-2a6e45171b8b@intel.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Fri, 21 Jul 2023 10:42:58 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Xiaoyao Li <xiaoyao.li@intel.com>\0" + "Cc\0Paolo Bonzini <pbonzini@redhat.com>" + Marc Zyngier <maz@kernel.org> + Oliver Upton <oliver.upton@linux.dev> + Huacai Chen <chenhuacai@kernel.org> + Michael Ellerman <mpe@ellerman.id.au> + Anup Patel <anup@brainfault.org> + Paul Walmsley <paul.walmsley@sifive.com> + Palmer Dabbelt <palmer@dabbelt.com> + Albert Ou <aou@eecs.berkeley.edu> + Matthew Wilcox (Oracle) <willy@infradead.org> + Andrew Morton <akpm@linux-foundation.org> + Paul Moore <paul@paul-moore.com> + James Morris <jmorris@namei.org> + Serge E. Hallyn <serge@hallyn.com> + kvm@vger.kernel.org + linux-arm-kernel@lists.infradead.org + kvmarm@lists.linux.dev + linux-mips@vger.kernel.org + linuxppc-dev@lists.ozlabs.org + kvm-riscv@lists.infradead.org + linux-riscv@lists.infradead.org + linux-fsdevel@vger.kernel.org + linux-mm@kvack.org + linux-security-module@vger.kernel.org + linux-kernel@vger.kernel.org + Chao Peng <chao.p.peng@linux.intel.com> + Fuad Tabba <tabba@google.com> + Jarkko Sakkinen <jarkko@kernel.org> + Yu Zhang <yu.c.zhang@linux.intel.com> + Vishal Annapurve <vannapurve@google.com> + Ackerley Tng <ackerleytng@google.com> + Maciej Szmigiero <mail@maciej.szmigiero.name> + Vlastimil Babka <vbabka@suse.cz> + David Hildenbrand <david@redhat.com> + Quentin Perret <qperret@google.com> + Michael Roth <michael.roth@amd.com> + Wang <wei.w.wang@intel.com> + Liam Merwick <liam.merwick@oracle.com> + Isaku Yamahata <isaku.yamahata@gmail.com> + " Kirill A . Shutemov <kirill.shutemov@linux.intel.com>\0" "\00:1\0" "b\0" "On Fri, Jul 21, 2023, Xiaoyao Li wrote:\n" @@ -13,17 +53,17 @@ "> > On 7/19/2023 7:44 AM, Sean Christopherson wrote:\n" "> > > @@ -6255,12 +6298,17 @@ int kvm_init(unsigned vcpu_size, unsigned\n" "> > > vcpu_align, struct module *module)\n" - "> > > ????? if (r)\n" - "> > > ????????? goto err_async_pf;\n" - "> > > +??? r = kvm_gmem_init();\n" - "> > > +??? if (r)\n" - "> > > +??????? goto err_gmem;\n" + "> > > \302\240\302\240\302\240\302\240\302\240 if (r)\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240 goto err_async_pf;\n" + "> > > +\302\240\302\240\302\240 r = kvm_gmem_init();\n" + "> > > +\302\240\302\240\302\240 if (r)\n" + "> > > +\302\240\302\240\302\240\302\240\302\240\302\240\302\240 goto err_gmem;\n" "> > > +\n" - "> > > ????? kvm_chardev_ops.owner = module;\n" - "> > > ????? kvm_preempt_ops.sched_in = kvm_sched_in;\n" - "> > > ????? kvm_preempt_ops.sched_out = kvm_sched_out;\n" - "> > > ????? kvm_init_debug();\n" - "> > > +??? kvm_gmem_init();\n" + "> > > \302\240\302\240\302\240\302\240\302\240 kvm_chardev_ops.owner = module;\n" + "> > > \302\240\302\240\302\240\302\240\302\240 kvm_preempt_ops.sched_in = kvm_sched_in;\n" + "> > > \302\240\302\240\302\240\302\240\302\240 kvm_preempt_ops.sched_out = kvm_sched_out;\n" + "> > > \302\240\302\240\302\240\302\240\302\240 kvm_init_debug();\n" + "> > > +\302\240\302\240\302\240 kvm_gmem_init();\n" "> > \n" "> > why kvm_gmem_init() needs to be called again? by mistake?\n" "> \n" @@ -38,4 +78,4 @@ "\n" Not worth investigating unless you want to satiate your curiosity :-) -7327043507c48a48e94b865ea06d1827bbf339a9940b279a573f42cd85f86acd +57e2caf1d83c1892129a5d5c8977be537f33fc5eba4705af32336f2b3740538f
diff --git a/a/1.txt b/N2/1.txt index 1680cf1..457f12a 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -3,17 +3,17 @@ On Fri, Jul 21, 2023, Xiaoyao Li wrote: > > On 7/19/2023 7:44 AM, Sean Christopherson wrote: > > > @@ -6255,12 +6298,17 @@ int kvm_init(unsigned vcpu_size, unsigned > > > vcpu_align, struct module *module) -> > > ????? if (r) -> > > ????????? goto err_async_pf; -> > > +??? r = kvm_gmem_init(); -> > > +??? if (r) -> > > +??????? goto err_gmem; +> > > if (r) +> > > goto err_async_pf; +> > > + r = kvm_gmem_init(); +> > > + if (r) +> > > + goto err_gmem; > > > + -> > > ????? kvm_chardev_ops.owner = module; -> > > ????? kvm_preempt_ops.sched_in = kvm_sched_in; -> > > ????? kvm_preempt_ops.sched_out = kvm_sched_out; -> > > ????? kvm_init_debug(); -> > > +??? kvm_gmem_init(); +> > > kvm_chardev_ops.owner = module; +> > > kvm_preempt_ops.sched_in = kvm_sched_in; +> > > kvm_preempt_ops.sched_out = kvm_sched_out; +> > > kvm_init_debug(); +> > > + kvm_gmem_init(); > > > > why kvm_gmem_init() needs to be called again? by mistake? > @@ -27,3 +27,8 @@ Yeah, definitely a bug. > the issue, though I'm not sure about the reason. Not worth investigating unless you want to satiate your curiosity :-) + +_______________________________________________ +linux-riscv mailing list +linux-riscv@lists.infradead.org +http://lists.infradead.org/mailman/listinfo/linux-riscv diff --git a/a/content_digest b/N2/content_digest index bbe2fb8..45c4d2f 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -3,9 +3,49 @@ "ref\0fdc155f5-041b-a1b1-15aa-8f970180a13a@intel.com\0" "ref\029baac45-7736-a28c-3b2d-2a6e45171b8b@intel.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Fri, 21 Jul 2023 10:42:58 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Xiaoyao Li <xiaoyao.li@intel.com>\0" + "Cc\0Paolo Bonzini <pbonzini@redhat.com>" + Marc Zyngier <maz@kernel.org> + Oliver Upton <oliver.upton@linux.dev> + Huacai Chen <chenhuacai@kernel.org> + Michael Ellerman <mpe@ellerman.id.au> + Anup Patel <anup@brainfault.org> + Paul Walmsley <paul.walmsley@sifive.com> + Palmer Dabbelt <palmer@dabbelt.com> + Albert Ou <aou@eecs.berkeley.edu> + Matthew Wilcox (Oracle) <willy@infradead.org> + Andrew Morton <akpm@linux-foundation.org> + Paul Moore <paul@paul-moore.com> + James Morris <jmorris@namei.org> + Serge E. Hallyn <serge@hallyn.com> + kvm@vger.kernel.org + linux-arm-kernel@lists.infradead.org + kvmarm@lists.linux.dev + linux-mips@vger.kernel.org + linuxppc-dev@lists.ozlabs.org + kvm-riscv@lists.infradead.org + linux-riscv@lists.infradead.org + linux-fsdevel@vger.kernel.org + linux-mm@kvack.org + linux-security-module@vger.kernel.org + linux-kernel@vger.kernel.org + Chao Peng <chao.p.peng@linux.intel.com> + Fuad Tabba <tabba@google.com> + Jarkko Sakkinen <jarkko@kernel.org> + Yu Zhang <yu.c.zhang@linux.intel.com> + Vishal Annapurve <vannapurve@google.com> + Ackerley Tng <ackerleytng@google.com> + Maciej Szmigiero <mail@maciej.szmigiero.name> + Vlastimil Babka <vbabka@suse.cz> + David Hildenbrand <david@redhat.com> + Quentin Perret <qperret@google.com> + Michael Roth <michael.roth@amd.com> + Wang <wei.w.wang@intel.com> + Liam Merwick <liam.merwick@oracle.com> + Isaku Yamahata <isaku.yamahata@gmail.com> + " Kirill A . Shutemov <kirill.shutemov@linux.intel.com>\0" "\00:1\0" "b\0" "On Fri, Jul 21, 2023, Xiaoyao Li wrote:\n" @@ -13,17 +53,17 @@ "> > On 7/19/2023 7:44 AM, Sean Christopherson wrote:\n" "> > > @@ -6255,12 +6298,17 @@ int kvm_init(unsigned vcpu_size, unsigned\n" "> > > vcpu_align, struct module *module)\n" - "> > > ????? if (r)\n" - "> > > ????????? goto err_async_pf;\n" - "> > > +??? r = kvm_gmem_init();\n" - "> > > +??? if (r)\n" - "> > > +??????? goto err_gmem;\n" + "> > > \302\240\302\240\302\240\302\240\302\240 if (r)\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240 goto err_async_pf;\n" + "> > > +\302\240\302\240\302\240 r = kvm_gmem_init();\n" + "> > > +\302\240\302\240\302\240 if (r)\n" + "> > > +\302\240\302\240\302\240\302\240\302\240\302\240\302\240 goto err_gmem;\n" "> > > +\n" - "> > > ????? kvm_chardev_ops.owner = module;\n" - "> > > ????? kvm_preempt_ops.sched_in = kvm_sched_in;\n" - "> > > ????? kvm_preempt_ops.sched_out = kvm_sched_out;\n" - "> > > ????? kvm_init_debug();\n" - "> > > +??? kvm_gmem_init();\n" + "> > > \302\240\302\240\302\240\302\240\302\240 kvm_chardev_ops.owner = module;\n" + "> > > \302\240\302\240\302\240\302\240\302\240 kvm_preempt_ops.sched_in = kvm_sched_in;\n" + "> > > \302\240\302\240\302\240\302\240\302\240 kvm_preempt_ops.sched_out = kvm_sched_out;\n" + "> > > \302\240\302\240\302\240\302\240\302\240 kvm_init_debug();\n" + "> > > +\302\240\302\240\302\240 kvm_gmem_init();\n" "> > \n" "> > why kvm_gmem_init() needs to be called again? by mistake?\n" "> \n" @@ -36,6 +76,11 @@ "> re-mapped infinitely. Removing the second call of kvm_gmem_init() can solve\n" "> the issue, though I'm not sure about the reason.\n" "\n" - Not worth investigating unless you want to satiate your curiosity :-) + "Not worth investigating unless you want to satiate your curiosity :-)\n" + "\n" + "_______________________________________________\n" + "linux-riscv mailing list\n" + "linux-riscv@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-riscv -7327043507c48a48e94b865ea06d1827bbf339a9940b279a573f42cd85f86acd +ffb03b5c33a532d516d77f9fe507411f581d856d1da057c5c87d0ac6f911394d
diff --git a/a/1.txt b/N3/1.txt index 1680cf1..a8914e0 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -3,17 +3,17 @@ On Fri, Jul 21, 2023, Xiaoyao Li wrote: > > On 7/19/2023 7:44 AM, Sean Christopherson wrote: > > > @@ -6255,12 +6298,17 @@ int kvm_init(unsigned vcpu_size, unsigned > > > vcpu_align, struct module *module) -> > > ????? if (r) -> > > ????????? goto err_async_pf; -> > > +??? r = kvm_gmem_init(); -> > > +??? if (r) -> > > +??????? goto err_gmem; +> > > if (r) +> > > goto err_async_pf; +> > > + r = kvm_gmem_init(); +> > > + if (r) +> > > + goto err_gmem; > > > + -> > > ????? kvm_chardev_ops.owner = module; -> > > ????? kvm_preempt_ops.sched_in = kvm_sched_in; -> > > ????? kvm_preempt_ops.sched_out = kvm_sched_out; -> > > ????? kvm_init_debug(); -> > > +??? kvm_gmem_init(); +> > > kvm_chardev_ops.owner = module; +> > > kvm_preempt_ops.sched_in = kvm_sched_in; +> > > kvm_preempt_ops.sched_out = kvm_sched_out; +> > > kvm_init_debug(); +> > > + kvm_gmem_init(); > > > > why kvm_gmem_init() needs to be called again? by mistake? > diff --git a/a/content_digest b/N3/content_digest index bbe2fb8..9dd63d9 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -3,9 +3,48 @@ "ref\0fdc155f5-041b-a1b1-15aa-8f970180a13a@intel.com\0" "ref\029baac45-7736-a28c-3b2d-2a6e45171b8b@intel.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Fri, 21 Jul 2023 10:42:58 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Xiaoyao Li <xiaoyao.li@intel.com>\0" + "Cc\0kvm@vger.kernel.org" + David Hildenbrand <david@redhat.com> + Yu Zhang <yu.c.zhang@linux.intel.com> + linux-kernel@vger.kernel.org + linux-mm@kvack.org + Chao Peng <chao.p.peng@linux.intel.com> + linux-riscv@lists.infradead.org + Isaku Yamahata <isaku.yamahata@gmail.com> + Paul Moore <paul@paul-moore.com> + Marc Zyngier <maz@kernel.org> + Huacai Chen <chenhuacai@kernel.org> + James Morris <jmorris@namei.org> + " Matthew Wilcox \\(Oracle\\) <willy@infradead.org>" + Wang <wei.w.wang@intel.com> + Fuad Tabba <tabba@google.com> + Jarkko Sakkinen <jarkko@kernel.org> + Serge E. Hallyn <serge@hallyn.com> + Maciej Szmigiero <mail@maciej.szmigiero.name> + Albert Ou <aou@eecs.berkeley.edu> + Vlastimil Babka <vbabka@suse.cz> + Michael Roth <michael.roth@amd.com> + Ackerley Tng <ackerleytng@google.com> + Paul Walmsley <paul.walmsley@sifive.com> + kvmarm@lists.linux.dev + linux-arm-kernel@lists.infradead.org + Quentin Perret <qperret@google.com> + Liam Merwick <liam.merwick@oracle.com> + linux-mips@vger.kernel.org + Oliver Upton <oliver.upton@linux.dev> + linux-security-module@vger.kernel.org + Palmer Dabbelt <palmer@dabbelt.com> + kvm-riscv@lists.infradead.org + Anup Patel <anup@brainfault.org> + linux-fsdevel@vger.kernel.org + Paolo Bonzini <pbonzini@redhat.com> + Andrew Morton <akpm@linux-foundation.org> + Vishal Annapurve <vannapurve@google.com> + linuxppc-dev@lists.ozlabs.org + " Kirill A . Shutemov <kirill.shutemov@linux.intel.com>\0" "\00:1\0" "b\0" "On Fri, Jul 21, 2023, Xiaoyao Li wrote:\n" @@ -13,17 +52,17 @@ "> > On 7/19/2023 7:44 AM, Sean Christopherson wrote:\n" "> > > @@ -6255,12 +6298,17 @@ int kvm_init(unsigned vcpu_size, unsigned\n" "> > > vcpu_align, struct module *module)\n" - "> > > ????? if (r)\n" - "> > > ????????? goto err_async_pf;\n" - "> > > +??? r = kvm_gmem_init();\n" - "> > > +??? if (r)\n" - "> > > +??????? goto err_gmem;\n" + "> > > \302\240\302\240\302\240\302\240\302\240 if (r)\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240 goto err_async_pf;\n" + "> > > +\302\240\302\240\302\240 r = kvm_gmem_init();\n" + "> > > +\302\240\302\240\302\240 if (r)\n" + "> > > +\302\240\302\240\302\240\302\240\302\240\302\240\302\240 goto err_gmem;\n" "> > > +\n" - "> > > ????? kvm_chardev_ops.owner = module;\n" - "> > > ????? kvm_preempt_ops.sched_in = kvm_sched_in;\n" - "> > > ????? kvm_preempt_ops.sched_out = kvm_sched_out;\n" - "> > > ????? kvm_init_debug();\n" - "> > > +??? kvm_gmem_init();\n" + "> > > \302\240\302\240\302\240\302\240\302\240 kvm_chardev_ops.owner = module;\n" + "> > > \302\240\302\240\302\240\302\240\302\240 kvm_preempt_ops.sched_in = kvm_sched_in;\n" + "> > > \302\240\302\240\302\240\302\240\302\240 kvm_preempt_ops.sched_out = kvm_sched_out;\n" + "> > > \302\240\302\240\302\240\302\240\302\240 kvm_init_debug();\n" + "> > > +\302\240\302\240\302\240 kvm_gmem_init();\n" "> > \n" "> > why kvm_gmem_init() needs to be called again? by mistake?\n" "> \n" @@ -38,4 +77,4 @@ "\n" Not worth investigating unless you want to satiate your curiosity :-) -7327043507c48a48e94b865ea06d1827bbf339a9940b279a573f42cd85f86acd +fb06df188bdfbc82c21b23f6fdcabaa5cb792f64e5c333843ccf3579994a7c97
diff --git a/a/1.txt b/N4/1.txt index 1680cf1..457fe0b 100644 --- a/a/1.txt +++ b/N4/1.txt @@ -3,17 +3,17 @@ On Fri, Jul 21, 2023, Xiaoyao Li wrote: > > On 7/19/2023 7:44 AM, Sean Christopherson wrote: > > > @@ -6255,12 +6298,17 @@ int kvm_init(unsigned vcpu_size, unsigned > > > vcpu_align, struct module *module) -> > > ????? if (r) -> > > ????????? goto err_async_pf; -> > > +??? r = kvm_gmem_init(); -> > > +??? if (r) -> > > +??????? goto err_gmem; +> > > if (r) +> > > goto err_async_pf; +> > > + r = kvm_gmem_init(); +> > > + if (r) +> > > + goto err_gmem; > > > + -> > > ????? kvm_chardev_ops.owner = module; -> > > ????? kvm_preempt_ops.sched_in = kvm_sched_in; -> > > ????? kvm_preempt_ops.sched_out = kvm_sched_out; -> > > ????? kvm_init_debug(); -> > > +??? kvm_gmem_init(); +> > > kvm_chardev_ops.owner = module; +> > > kvm_preempt_ops.sched_in = kvm_sched_in; +> > > kvm_preempt_ops.sched_out = kvm_sched_out; +> > > kvm_init_debug(); +> > > + kvm_gmem_init(); > > > > why kvm_gmem_init() needs to be called again? by mistake? > @@ -27,3 +27,8 @@ Yeah, definitely a bug. > the issue, though I'm not sure about the reason. Not worth investigating unless you want to satiate your curiosity :-) + +_______________________________________________ +linux-arm-kernel mailing list +linux-arm-kernel@lists.infradead.org +http://lists.infradead.org/mailman/listinfo/linux-arm-kernel diff --git a/a/content_digest b/N4/content_digest index bbe2fb8..c068c67 100644 --- a/a/content_digest +++ b/N4/content_digest @@ -3,9 +3,49 @@ "ref\0fdc155f5-041b-a1b1-15aa-8f970180a13a@intel.com\0" "ref\029baac45-7736-a28c-3b2d-2a6e45171b8b@intel.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Fri, 21 Jul 2023 10:42:58 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Xiaoyao Li <xiaoyao.li@intel.com>\0" + "Cc\0Paolo Bonzini <pbonzini@redhat.com>" + Marc Zyngier <maz@kernel.org> + Oliver Upton <oliver.upton@linux.dev> + Huacai Chen <chenhuacai@kernel.org> + Michael Ellerman <mpe@ellerman.id.au> + Anup Patel <anup@brainfault.org> + Paul Walmsley <paul.walmsley@sifive.com> + Palmer Dabbelt <palmer@dabbelt.com> + Albert Ou <aou@eecs.berkeley.edu> + Matthew Wilcox (Oracle) <willy@infradead.org> + Andrew Morton <akpm@linux-foundation.org> + Paul Moore <paul@paul-moore.com> + James Morris <jmorris@namei.org> + Serge E. Hallyn <serge@hallyn.com> + kvm@vger.kernel.org + linux-arm-kernel@lists.infradead.org + kvmarm@lists.linux.dev + linux-mips@vger.kernel.org + linuxppc-dev@lists.ozlabs.org + kvm-riscv@lists.infradead.org + linux-riscv@lists.infradead.org + linux-fsdevel@vger.kernel.org + linux-mm@kvack.org + linux-security-module@vger.kernel.org + linux-kernel@vger.kernel.org + Chao Peng <chao.p.peng@linux.intel.com> + Fuad Tabba <tabba@google.com> + Jarkko Sakkinen <jarkko@kernel.org> + Yu Zhang <yu.c.zhang@linux.intel.com> + Vishal Annapurve <vannapurve@google.com> + Ackerley Tng <ackerleytng@google.com> + Maciej Szmigiero <mail@maciej.szmigiero.name> + Vlastimil Babka <vbabka@suse.cz> + David Hildenbrand <david@redhat.com> + Quentin Perret <qperret@google.com> + Michael Roth <michael.roth@amd.com> + Wang <wei.w.wang@intel.com> + Liam Merwick <liam.merwick@oracle.com> + Isaku Yamahata <isaku.yamahata@gmail.com> + " Kirill A . Shutemov <kirill.shutemov@linux.intel.com>\0" "\00:1\0" "b\0" "On Fri, Jul 21, 2023, Xiaoyao Li wrote:\n" @@ -13,17 +53,17 @@ "> > On 7/19/2023 7:44 AM, Sean Christopherson wrote:\n" "> > > @@ -6255,12 +6298,17 @@ int kvm_init(unsigned vcpu_size, unsigned\n" "> > > vcpu_align, struct module *module)\n" - "> > > ????? if (r)\n" - "> > > ????????? goto err_async_pf;\n" - "> > > +??? r = kvm_gmem_init();\n" - "> > > +??? if (r)\n" - "> > > +??????? goto err_gmem;\n" + "> > > \302\240\302\240\302\240\302\240\302\240 if (r)\n" + "> > > \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240 goto err_async_pf;\n" + "> > > +\302\240\302\240\302\240 r = kvm_gmem_init();\n" + "> > > +\302\240\302\240\302\240 if (r)\n" + "> > > +\302\240\302\240\302\240\302\240\302\240\302\240\302\240 goto err_gmem;\n" "> > > +\n" - "> > > ????? kvm_chardev_ops.owner = module;\n" - "> > > ????? kvm_preempt_ops.sched_in = kvm_sched_in;\n" - "> > > ????? kvm_preempt_ops.sched_out = kvm_sched_out;\n" - "> > > ????? kvm_init_debug();\n" - "> > > +??? kvm_gmem_init();\n" + "> > > \302\240\302\240\302\240\302\240\302\240 kvm_chardev_ops.owner = module;\n" + "> > > \302\240\302\240\302\240\302\240\302\240 kvm_preempt_ops.sched_in = kvm_sched_in;\n" + "> > > \302\240\302\240\302\240\302\240\302\240 kvm_preempt_ops.sched_out = kvm_sched_out;\n" + "> > > \302\240\302\240\302\240\302\240\302\240 kvm_init_debug();\n" + "> > > +\302\240\302\240\302\240 kvm_gmem_init();\n" "> > \n" "> > why kvm_gmem_init() needs to be called again? by mistake?\n" "> \n" @@ -36,6 +76,11 @@ "> re-mapped infinitely. Removing the second call of kvm_gmem_init() can solve\n" "> the issue, though I'm not sure about the reason.\n" "\n" - Not worth investigating unless you want to satiate your curiosity :-) + "Not worth investigating unless you want to satiate your curiosity :-)\n" + "\n" + "_______________________________________________\n" + "linux-arm-kernel mailing list\n" + "linux-arm-kernel@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -7327043507c48a48e94b865ea06d1827bbf339a9940b279a573f42cd85f86acd +ff4171a0e1f6643149e56c8dbdf3c64406628277f58b450e98f168ff2f26358c
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.