From: Paolo Bonzini <pbonzini@redhat.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Wanpeng Li <wanpengli@tencent.com>,
kvm@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Guo Ren <guoren@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
linux-riscv@lists.infradead.org,
Vincent Chen <deanbo422@gmail.com>, Jiri Olsa <jolsa@redhat.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org, Will Deacon <will@kernel.org>,
Joerg Roedel <joro@8bytes.org>,
x86@kernel.org, linux-csky@vger.kernel.org,
kvmarm@lists.cs.columbia.edu,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>, Like Xu <like.xu.linux@gmail.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Zhu Lingshan <lingshan.zhu@intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Borislav Petkov <bp@alien8.de>, Greentime Hu <green.hu@gmail.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Namhyung Kim <namhyung@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Artem Kashkanov <artem.kashkanov@intel.com>,
linux-arm-kernel@lists.infradead.org,
Jim Mattson <jmattson@google.com>,
Juergen Gross <jgross@suse.com>, Nick Hu <nickhu@andestech.com>,
Sean Christopherson <seanjc@google.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Palmer Dabbelt <palmer@dabbelt.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>
Subject: Re: [PATCH v2 00/13] perf: KVM: Fix, optimize, and clean up callbacks
Date: Mon, 20 Sep 2021 20:22:50 +0200 [thread overview]
Message-ID: <0eb2d4b1-23a4-c318-9f91-8dce78c6c8ad@redhat.com> (raw)
In-Reply-To: <87o88nuzzc.wl-maz@kernel.org>
On 20/09/21 15:40, Marc Zyngier wrote:
>>> At least not before we
>>> declare the arm64 single kernel image policy to be obsolete.
>>
>> --verbose please.:) I am sure you're right, but I don't understand
>> the link between the two.
>
> To start making KVM/arm64 modular, you'd have to build it such as
> there is no support for the nVHE hypervisor anymore. Which would mean
> two different configs (one that can only work with VHE, and one for
> the rest) and contradicts the current single kernel image policy.
Ah okay, I interpreted the policy as "it's possible to build a single
kernel image but it would be possible to build an image for a subset of
the features as well".
In that case you could have one config that can work either with or
without VHE (and supports y/n) and one config that can only work with
VHE (and supports y/m/n). The code to enter VHE EL2 would of course
always be builtin.
> It is bad enough that we have to support 3 sets of page sizes.
> Doubling the validation space for the sake of being able to unload KVM
> seems a dubious prospect.
It's not even a configuration that matches kconfig very well, since it
does have a way to build something *only as a module*, but not a way to
build something only as built-in.
That said, if you had the possibility to unload/reload KVM, you'll
quickly become unable to live without it. :)
Paolo
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Sean Christopherson <seanjc@google.com>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Guo Ren <guoren@kernel.org>, Nick Hu <nickhu@andestech.com>,
Greentime Hu <green.hu@gmail.com>,
Vincent Chen <deanbo422@gmail.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
x86@kernel.org, Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Stefano Stabellini <sstabellini@kernel.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, linux-csky@vger.kernel.org,
linux-riscv@lists.infradead.org, kvm@vger.kernel.org,
xen-devel@lists.xenproject.org,
Artem Kashkanov <artem.kashkanov@intel.com>,
Like Xu <like.xu.linux@gmail.com>,
Zhu Lingshan <lingshan.zhu@intel.com>
Subject: Re: [PATCH v2 00/13] perf: KVM: Fix, optimize, and clean up callbacks
Date: Mon, 20 Sep 2021 20:22:50 +0200 [thread overview]
Message-ID: <0eb2d4b1-23a4-c318-9f91-8dce78c6c8ad@redhat.com> (raw)
In-Reply-To: <87o88nuzzc.wl-maz@kernel.org>
On 20/09/21 15:40, Marc Zyngier wrote:
>>> At least not before we
>>> declare the arm64 single kernel image policy to be obsolete.
>>
>> --verbose please.:) I am sure you're right, but I don't understand
>> the link between the two.
>
> To start making KVM/arm64 modular, you'd have to build it such as
> there is no support for the nVHE hypervisor anymore. Which would mean
> two different configs (one that can only work with VHE, and one for
> the rest) and contradicts the current single kernel image policy.
Ah okay, I interpreted the policy as "it's possible to build a single
kernel image but it would be possible to build an image for a subset of
the features as well".
In that case you could have one config that can work either with or
without VHE (and supports y/n) and one config that can only work with
VHE (and supports y/m/n). The code to enter VHE EL2 would of course
always be builtin.
> It is bad enough that we have to support 3 sets of page sizes.
> Doubling the validation space for the sake of being able to unload KVM
> seems a dubious prospect.
It's not even a configuration that matches kconfig very well, since it
does have a way to build something *only as a module*, but not a way to
build something only as built-in.
That said, if you had the possibility to unload/reload KVM, you'll
quickly become unable to live without it. :)
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Sean Christopherson <seanjc@google.com>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Guo Ren <guoren@kernel.org>, Nick Hu <nickhu@andestech.com>,
Greentime Hu <green.hu@gmail.com>,
Vincent Chen <deanbo422@gmail.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
x86@kernel.org, Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Stefano Stabellini <sstabellini@kernel.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, linux-csky@vger.kernel.org,
linux-riscv@lists.infradead.org, kvm@vger.kernel.org,
xen-devel@lists.xenproject.org,
Artem Kashkanov <artem.kashkanov@intel.com>,
Like Xu <like.xu.linux@gmail.com>,
Zhu Lingshan <lingshan.zhu@intel.com>
Subject: Re: [PATCH v2 00/13] perf: KVM: Fix, optimize, and clean up callbacks
Date: Mon, 20 Sep 2021 20:22:50 +0200 [thread overview]
Message-ID: <0eb2d4b1-23a4-c318-9f91-8dce78c6c8ad@redhat.com> (raw)
In-Reply-To: <87o88nuzzc.wl-maz@kernel.org>
On 20/09/21 15:40, Marc Zyngier wrote:
>>> At least not before we
>>> declare the arm64 single kernel image policy to be obsolete.
>>
>> --verbose please.:) I am sure you're right, but I don't understand
>> the link between the two.
>
> To start making KVM/arm64 modular, you'd have to build it such as
> there is no support for the nVHE hypervisor anymore. Which would mean
> two different configs (one that can only work with VHE, and one for
> the rest) and contradicts the current single kernel image policy.
Ah okay, I interpreted the policy as "it's possible to build a single
kernel image but it would be possible to build an image for a subset of
the features as well".
In that case you could have one config that can work either with or
without VHE (and supports y/n) and one config that can only work with
VHE (and supports y/m/n). The code to enter VHE EL2 would of course
always be builtin.
> It is bad enough that we have to support 3 sets of page sizes.
> Doubling the validation space for the sake of being able to unload KVM
> seems a dubious prospect.
It's not even a configuration that matches kconfig very well, since it
does have a way to build something *only as a module*, but not a way to
build something only as built-in.
That said, if you had the possibility to unload/reload KVM, you'll
quickly become unable to live without it. :)
Paolo
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Sean Christopherson <seanjc@google.com>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Guo Ren <guoren@kernel.org>, Nick Hu <nickhu@andestech.com>,
Greentime Hu <green.hu@gmail.com>,
Vincent Chen <deanbo422@gmail.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
x86@kernel.org, Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Stefano Stabellini <sstabellini@kernel.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, linux-csky@vger.kernel.org,
linux-riscv@lists.infradead.org, kvm@vger.kernel.org,
xen-devel@lists.xenproject.org,
Artem Kashkanov <artem.kashkanov@intel.com>,
Like Xu <like.xu.linux@gmail.com>,
Zhu Lingshan <lingshan.zhu@intel.com>
Subject: Re: [PATCH v2 00/13] perf: KVM: Fix, optimize, and clean up callbacks
Date: Mon, 20 Sep 2021 20:22:50 +0200 [thread overview]
Message-ID: <0eb2d4b1-23a4-c318-9f91-8dce78c6c8ad@redhat.com> (raw)
In-Reply-To: <87o88nuzzc.wl-maz@kernel.org>
On 20/09/21 15:40, Marc Zyngier wrote:
>>> At least not before we
>>> declare the arm64 single kernel image policy to be obsolete.
>>
>> --verbose please.:) I am sure you're right, but I don't understand
>> the link between the two.
>
> To start making KVM/arm64 modular, you'd have to build it such as
> there is no support for the nVHE hypervisor anymore. Which would mean
> two different configs (one that can only work with VHE, and one for
> the rest) and contradicts the current single kernel image policy.
Ah okay, I interpreted the policy as "it's possible to build a single
kernel image but it would be possible to build an image for a subset of
the features as well".
In that case you could have one config that can work either with or
without VHE (and supports y/n) and one config that can only work with
VHE (and supports y/m/n). The code to enter VHE EL2 would of course
always be builtin.
> It is bad enough that we have to support 3 sets of page sizes.
> Doubling the validation space for the sake of being able to unload KVM
> seems a dubious prospect.
It's not even a configuration that matches kconfig very well, since it
does have a way to build something *only as a module*, but not a way to
build something only as built-in.
That said, if you had the possibility to unload/reload KVM, you'll
quickly become unable to live without it. :)
Paolo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-09-20 18:23 UTC|newest]
Thread overview: 130+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-28 0:35 [PATCH v2 00/13] perf: KVM: Fix, optimize, and clean up callbacks Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` [PATCH v2 01/13] perf: Ensure perf_guest_cbs aren't reloaded between !NULL check and deref Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 19:44 ` Peter Zijlstra
2021-08-28 19:44 ` Peter Zijlstra
2021-08-28 19:44 ` Peter Zijlstra
2021-08-28 19:44 ` Peter Zijlstra
2021-09-16 21:41 ` Sean Christopherson
2021-09-16 21:41 ` Sean Christopherson
2021-09-16 21:41 ` Sean Christopherson
2021-09-16 21:41 ` Sean Christopherson
2021-08-28 0:35 ` [PATCH v2 02/13] KVM: x86: Register perf callbacks after calling vendor's hardware_setup() Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` [PATCH v2 03/13] KVM: x86: Register Processor Trace interrupt hook iff PT enabled in guest Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` [PATCH v2 04/13] perf: Stop pretending that perf can handle multiple guest callbacks Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` [PATCH v2 05/13] perf: Force architectures to opt-in to " Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 19:47 ` Peter Zijlstra
2021-08-28 19:47 ` Peter Zijlstra
2021-08-28 19:47 ` Peter Zijlstra
2021-08-28 19:47 ` Peter Zijlstra
2021-09-16 22:30 ` Sean Christopherson
2021-09-16 22:30 ` Sean Christopherson
2021-09-16 22:30 ` Sean Christopherson
2021-09-16 22:30 ` Sean Christopherson
2021-09-21 16:44 ` Paolo Bonzini
2021-09-21 16:44 ` Paolo Bonzini
2021-09-21 16:44 ` Paolo Bonzini
2021-09-21 16:44 ` Paolo Bonzini
2021-09-21 21:29 ` Sean Christopherson
2021-09-21 21:29 ` Sean Christopherson
2021-09-21 21:29 ` Sean Christopherson
2021-09-21 21:29 ` Sean Christopherson
2021-08-28 0:35 ` [PATCH v2 06/13] perf/core: Rework guest callbacks to prepare for static_call support Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` [PATCH v2 07/13] perf/core: Use static_call to optimize perf_guest_info_callbacks Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` [PATCH v2 08/13] KVM: x86: Drop current_vcpu for kvm_running_vcpu + kvm_arch_vcpu variable Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` [PATCH v2 09/13] KVM: x86: More precisely identify NMI from guest when handling PMI Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` [PATCH v2 10/13] KVM: Move x86's perf guest info callbacks to generic KVM Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` [PATCH v2 11/13] KVM: x86: Move Intel Processor Trace interrupt handler to vmx.c Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` [PATCH v2 12/13] KVM: arm64: Convert to the generic perf callbacks Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` [PATCH v2 13/13] KVM: arm64: Drop perf.c and fold its tiny bits of code into arm.c / pmu.c Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 0:35 ` Sean Christopherson
2021-08-28 20:13 ` [PATCH v2 00/13] perf: KVM: Fix, optimize, and clean up callbacks Peter Zijlstra
2021-08-28 20:13 ` Peter Zijlstra
2021-08-28 20:13 ` Peter Zijlstra
2021-08-28 20:13 ` Peter Zijlstra
2021-09-16 21:37 ` Sean Christopherson
2021-09-16 21:37 ` Sean Christopherson
2021-09-16 21:37 ` Sean Christopherson
2021-09-16 21:37 ` Sean Christopherson
2021-09-17 7:28 ` Peter Zijlstra
2021-09-17 7:28 ` Peter Zijlstra
2021-09-17 7:28 ` Peter Zijlstra
2021-09-17 7:28 ` Peter Zijlstra
2021-09-17 16:53 ` Sean Christopherson
2021-09-17 16:53 ` Sean Christopherson
2021-09-17 16:53 ` Sean Christopherson
2021-09-17 16:53 ` Sean Christopherson
2021-09-20 12:05 ` Paolo Bonzini
2021-09-20 12:05 ` Paolo Bonzini
2021-09-20 12:05 ` Paolo Bonzini
2021-09-20 12:05 ` Paolo Bonzini
2021-09-20 12:22 ` Marc Zyngier
2021-09-20 12:22 ` Marc Zyngier
2021-09-20 12:22 ` Marc Zyngier
2021-09-20 12:22 ` Marc Zyngier
2021-09-20 13:18 ` Paolo Bonzini
2021-09-20 13:18 ` Paolo Bonzini
2021-09-20 13:18 ` Paolo Bonzini
2021-09-20 13:18 ` Paolo Bonzini
2021-09-20 13:40 ` Marc Zyngier
2021-09-20 13:40 ` Marc Zyngier
2021-09-20 13:40 ` Marc Zyngier
2021-09-20 13:40 ` Marc Zyngier
2021-09-20 18:22 ` Paolo Bonzini [this message]
2021-09-20 18:22 ` Paolo Bonzini
2021-09-20 18:22 ` Paolo Bonzini
2021-09-20 18:22 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0eb2d4b1-23a4-c318-9f91-8dce78c6c8ad@redhat.com \
--to=pbonzini@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=artem.kashkanov@intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=deanbo422@gmail.com \
--cc=green.hu@gmail.com \
--cc=guoren@kernel.org \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jmattson@google.com \
--cc=jolsa@redhat.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=like.xu.linux@gmail.com \
--cc=lingshan.zhu@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nickhu@andestech.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.