From: Sean Christopherson <seanjc@google.com>
To: kvm-riscv@lists.infradead.org
Subject: [PATCH v7 04/12] KVM: Allow range-based TLB invalidation from common code
Date: Mon, 31 Jul 2023 14:55:14 -0700 [thread overview]
Message-ID: <ZMgtwp/YCZciRvdr@google.com> (raw)
In-Reply-To: <20230722022251.3446223-5-rananta@google.com>
On Sat, Jul 22, 2023, Raghavendra Rao Ananta wrote:
> diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c
> index ec169f5c7dce..eb88d25f9896 100644
> --- a/arch/x86/kvm/mmu/mmu.c
> +++ b/arch/x86/kvm/mmu/mmu.c
> @@ -278,16 +278,15 @@ static inline bool kvm_available_flush_remote_tlbs_range(void)
> return kvm_x86_ops.flush_remote_tlbs_range;
> }
>
> -void kvm_flush_remote_tlbs_range(struct kvm *kvm, gfn_t start_gfn,
> - gfn_t nr_pages)
> +int kvm_arch_flush_remote_tlbs_range(struct kvm *kvm, gfn_t start_gfn, u64 pages)
Please keep "nr_pages", I have a very strong preference for that over just "pages"
as the "nr_" makes it super obvious that it's a single number, as opposed to an
array of pages or something.
And it doesn't truly matter, but IMO the gfn_t type is more appropriate since
the gfn and the number of pages need to have the same type.
WARNING: multiple messages have this Message-ID (diff)
From: Sean Christopherson <seanjc@google.com>
To: Raghavendra Rao Ananta <rananta@google.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Huacai Chen <chenhuacai@kernel.org>,
Zenghui Yu <yuzenghui@huawei.com>,
Anup Patel <anup@brainfault.org>,
Atish Patra <atishp@atishpatra.org>,
Jing Zhang <jingzhangos@google.com>,
Reiji Watanabe <reijiw@google.com>,
Colton Lewis <coltonlewis@google.com>,
David Matlack <dmatlack@google.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-mips@vger.kernel.org, kvm-riscv@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, Gavin Shan <gshan@redhat.com>,
Shaoqin Huang <shahuang@redhat.com>
Subject: Re: [PATCH v7 04/12] KVM: Allow range-based TLB invalidation from common code
Date: Mon, 31 Jul 2023 14:55:14 -0700 [thread overview]
Message-ID: <ZMgtwp/YCZciRvdr@google.com> (raw)
In-Reply-To: <20230722022251.3446223-5-rananta@google.com>
On Sat, Jul 22, 2023, Raghavendra Rao Ananta wrote:
> diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c
> index ec169f5c7dce..eb88d25f9896 100644
> --- a/arch/x86/kvm/mmu/mmu.c
> +++ b/arch/x86/kvm/mmu/mmu.c
> @@ -278,16 +278,15 @@ static inline bool kvm_available_flush_remote_tlbs_range(void)
> return kvm_x86_ops.flush_remote_tlbs_range;
> }
>
> -void kvm_flush_remote_tlbs_range(struct kvm *kvm, gfn_t start_gfn,
> - gfn_t nr_pages)
> +int kvm_arch_flush_remote_tlbs_range(struct kvm *kvm, gfn_t start_gfn, u64 pages)
Please keep "nr_pages", I have a very strong preference for that over just "pages"
as the "nr_" makes it super obvious that it's a single number, as opposed to an
array of pages or something.
And it doesn't truly matter, but IMO the gfn_t type is more appropriate since
the gfn and the number of pages need to have the same type.
WARNING: multiple messages have this Message-ID (diff)
From: Sean Christopherson <seanjc@google.com>
To: Raghavendra Rao Ananta <rananta@google.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Huacai Chen <chenhuacai@kernel.org>,
Zenghui Yu <yuzenghui@huawei.com>,
Anup Patel <anup@brainfault.org>,
Atish Patra <atishp@atishpatra.org>,
Jing Zhang <jingzhangos@google.com>,
Reiji Watanabe <reijiw@google.com>,
Colton Lewis <coltonlewis@google.com>,
David Matlack <dmatlack@google.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-mips@vger.kernel.org, kvm-riscv@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, Gavin Shan <gshan@redhat.com>,
Shaoqin Huang <shahuang@redhat.com>
Subject: Re: [PATCH v7 04/12] KVM: Allow range-based TLB invalidation from common code
Date: Mon, 31 Jul 2023 14:55:14 -0700 [thread overview]
Message-ID: <ZMgtwp/YCZciRvdr@google.com> (raw)
In-Reply-To: <20230722022251.3446223-5-rananta@google.com>
On Sat, Jul 22, 2023, Raghavendra Rao Ananta wrote:
> diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c
> index ec169f5c7dce..eb88d25f9896 100644
> --- a/arch/x86/kvm/mmu/mmu.c
> +++ b/arch/x86/kvm/mmu/mmu.c
> @@ -278,16 +278,15 @@ static inline bool kvm_available_flush_remote_tlbs_range(void)
> return kvm_x86_ops.flush_remote_tlbs_range;
> }
>
> -void kvm_flush_remote_tlbs_range(struct kvm *kvm, gfn_t start_gfn,
> - gfn_t nr_pages)
> +int kvm_arch_flush_remote_tlbs_range(struct kvm *kvm, gfn_t start_gfn, u64 pages)
Please keep "nr_pages", I have a very strong preference for that over just "pages"
as the "nr_" makes it super obvious that it's a single number, as opposed to an
array of pages or something.
And it doesn't truly matter, but IMO the gfn_t type is more appropriate since
the gfn and the number of pages need to have the same type.
_______________________________________________
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: Sean Christopherson <seanjc@google.com>
To: Raghavendra Rao Ananta <rananta@google.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Huacai Chen <chenhuacai@kernel.org>,
Zenghui Yu <yuzenghui@huawei.com>,
Anup Patel <anup@brainfault.org>,
Atish Patra <atishp@atishpatra.org>,
Jing Zhang <jingzhangos@google.com>,
Reiji Watanabe <reijiw@google.com>,
Colton Lewis <coltonlewis@google.com>,
David Matlack <dmatlack@google.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-mips@vger.kernel.org, kvm-riscv@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, Gavin Shan <gshan@redhat.com>,
Shaoqin Huang <shahuang@redhat.com>
Subject: Re: [PATCH v7 04/12] KVM: Allow range-based TLB invalidation from common code
Date: Mon, 31 Jul 2023 14:55:14 -0700 [thread overview]
Message-ID: <ZMgtwp/YCZciRvdr@google.com> (raw)
In-Reply-To: <20230722022251.3446223-5-rananta@google.com>
On Sat, Jul 22, 2023, Raghavendra Rao Ananta wrote:
> diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c
> index ec169f5c7dce..eb88d25f9896 100644
> --- a/arch/x86/kvm/mmu/mmu.c
> +++ b/arch/x86/kvm/mmu/mmu.c
> @@ -278,16 +278,15 @@ static inline bool kvm_available_flush_remote_tlbs_range(void)
> return kvm_x86_ops.flush_remote_tlbs_range;
> }
>
> -void kvm_flush_remote_tlbs_range(struct kvm *kvm, gfn_t start_gfn,
> - gfn_t nr_pages)
> +int kvm_arch_flush_remote_tlbs_range(struct kvm *kvm, gfn_t start_gfn, u64 pages)
Please keep "nr_pages", I have a very strong preference for that over just "pages"
as the "nr_" makes it super obvious that it's a single number, as opposed to an
array of pages or something.
And it doesn't truly matter, but IMO the gfn_t type is more appropriate since
the gfn and the number of pages need to have the same type.
_______________________________________________
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:[~2023-07-31 21:55 UTC|newest]
Thread overview: 228+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 2:22 [PATCH v7 00/12] KVM: arm64: Add support for FEAT_TLBIRANGE Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` [PATCH v7 01/12] KVM: Rename kvm_arch_flush_remote_tlb() to kvm_arch_flush_remote_tlbs() Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-27 10:24 ` Marc Zyngier
2023-07-27 10:24 ` Marc Zyngier
2023-07-27 10:24 ` Marc Zyngier
2023-07-27 10:24 ` Marc Zyngier
2023-07-31 17:21 ` Raghavendra Rao Ananta
2023-07-31 17:21 ` Raghavendra Rao Ananta
2023-07-31 17:21 ` Raghavendra Rao Ananta
2023-07-31 17:21 ` Raghavendra Rao Ananta
2023-07-31 21:42 ` Sean Christopherson
2023-07-31 21:42 ` Sean Christopherson
2023-07-31 21:42 ` Sean Christopherson
2023-07-31 21:42 ` Sean Christopherson
2023-08-01 0:42 ` Raghavendra Rao Ananta
2023-08-01 0:42 ` Raghavendra Rao Ananta
2023-08-01 0:42 ` Raghavendra Rao Ananta
2023-08-01 0:42 ` Raghavendra Rao Ananta
2023-08-02 15:54 ` Marc Zyngier
2023-08-02 15:54 ` Marc Zyngier
2023-08-02 15:54 ` Marc Zyngier
2023-08-02 15:54 ` Marc Zyngier
2023-08-02 16:10 ` Sean Christopherson
2023-08-02 16:10 ` Sean Christopherson
2023-08-02 16:10 ` Sean Christopherson
2023-08-02 16:10 ` Sean Christopherson
2023-08-02 23:30 ` Raghavendra Rao Ananta
2023-08-02 23:30 ` Raghavendra Rao Ananta
2023-08-02 23:30 ` Raghavendra Rao Ananta
2023-08-02 23:30 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` [PATCH v7 02/12] KVM: arm64: Use kvm_arch_flush_remote_tlbs() Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-24 9:13 ` Shaoqin Huang
2023-07-24 9:13 ` Shaoqin Huang
2023-07-24 9:13 ` Shaoqin Huang
2023-07-27 10:25 ` Marc Zyngier
2023-07-27 10:25 ` Marc Zyngier
2023-07-27 10:25 ` Marc Zyngier
2023-07-27 10:25 ` Marc Zyngier
2023-07-31 21:50 ` Sean Christopherson
2023-07-31 21:50 ` Sean Christopherson
2023-07-31 21:50 ` Sean Christopherson
2023-07-31 21:50 ` Sean Christopherson
2023-08-02 15:55 ` Marc Zyngier
2023-08-02 15:55 ` Marc Zyngier
2023-08-02 15:55 ` Marc Zyngier
2023-08-02 15:55 ` Marc Zyngier
2023-08-02 23:28 ` Raghavendra Rao Ananta
2023-08-02 23:28 ` Raghavendra Rao Ananta
2023-08-02 23:28 ` Raghavendra Rao Ananta
2023-08-02 23:28 ` Raghavendra Rao Ananta
2023-08-04 18:19 ` Raghavendra Rao Ananta
2023-08-04 18:19 ` Raghavendra Rao Ananta
2023-08-04 18:19 ` Raghavendra Rao Ananta
2023-08-04 18:19 ` Raghavendra Rao Ananta
2023-08-08 15:07 ` Sean Christopherson
2023-08-08 15:07 ` Sean Christopherson
2023-08-08 15:07 ` Sean Christopherson
2023-08-08 15:07 ` Sean Christopherson
2023-08-08 16:19 ` Raghavendra Rao Ananta
2023-08-08 16:19 ` Raghavendra Rao Ananta
2023-08-08 16:19 ` Raghavendra Rao Ananta
2023-08-08 16:19 ` Raghavendra Rao Ananta
2023-08-08 16:43 ` Marc Zyngier
2023-08-08 16:43 ` Marc Zyngier
2023-08-08 16:43 ` Marc Zyngier
2023-08-08 16:43 ` Marc Zyngier
2023-08-08 16:46 ` Raghavendra Rao Ananta
2023-08-08 16:46 ` Raghavendra Rao Ananta
2023-08-08 16:46 ` Raghavendra Rao Ananta
2023-08-08 16:46 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` [PATCH v7 03/12] KVM: Remove CONFIG_HAVE_KVM_ARCH_TLB_FLUSH_ALL Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-24 9:13 ` Shaoqin Huang
2023-07-24 9:13 ` Shaoqin Huang
2023-07-24 9:13 ` Shaoqin Huang
2023-07-22 2:22 ` [PATCH v7 04/12] KVM: Allow range-based TLB invalidation from common code Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-31 21:55 ` Sean Christopherson [this message]
2023-07-31 21:55 ` Sean Christopherson
2023-07-31 21:55 ` Sean Christopherson
2023-07-31 21:55 ` Sean Christopherson
2023-08-01 0:39 ` Raghavendra Rao Ananta
2023-08-01 0:39 ` Raghavendra Rao Ananta
2023-08-01 0:39 ` Raghavendra Rao Ananta
2023-08-01 0:39 ` Raghavendra Rao Ananta
2023-08-07 4:06 ` Anup Patel
2023-08-07 4:06 ` Anup Patel
2023-08-07 4:06 ` Anup Patel
2023-08-07 4:06 ` Anup Patel
2023-07-22 2:22 ` [PATCH v7 05/12] KVM: Move kvm_arch_flush_remote_tlbs_memslot() to " Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-27 10:53 ` Marc Zyngier
2023-07-27 10:53 ` Marc Zyngier
2023-07-27 10:53 ` Marc Zyngier
2023-07-27 10:53 ` Marc Zyngier
2023-07-31 17:30 ` Raghavendra Rao Ananta
2023-07-31 17:30 ` Raghavendra Rao Ananta
2023-07-31 17:30 ` Raghavendra Rao Ananta
2023-07-31 17:30 ` Raghavendra Rao Ananta
2023-08-07 4:06 ` Anup Patel
2023-08-07 4:06 ` Anup Patel
2023-08-07 4:06 ` Anup Patel
2023-08-07 4:06 ` Anup Patel
2023-07-22 2:22 ` [PATCH v7 06/12] arm64: tlb: Refactor the core flush algorithm of __flush_tlb_range Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-27 10:58 ` Marc Zyngier
2023-07-27 10:58 ` Marc Zyngier
2023-07-27 10:58 ` Marc Zyngier
2023-07-27 10:58 ` Marc Zyngier
2023-07-31 17:36 ` Raghavendra Rao Ananta
2023-07-31 17:36 ` Raghavendra Rao Ananta
2023-07-31 17:36 ` Raghavendra Rao Ananta
2023-07-31 17:36 ` Raghavendra Rao Ananta
2023-08-02 15:58 ` Marc Zyngier
2023-08-02 15:58 ` Marc Zyngier
2023-08-02 15:58 ` Marc Zyngier
2023-08-02 15:58 ` Marc Zyngier
2023-08-02 23:31 ` Raghavendra Rao Ananta
2023-08-02 23:31 ` Raghavendra Rao Ananta
2023-08-02 23:31 ` Raghavendra Rao Ananta
2023-08-02 23:31 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` [PATCH v7 07/12] KVM: arm64: Implement __kvm_tlb_flush_vmid_range() Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-24 9:21 ` Shaoqin Huang
2023-07-24 9:21 ` Shaoqin Huang
2023-07-24 9:21 ` Shaoqin Huang
2023-07-27 12:40 ` Marc Zyngier
2023-07-27 12:40 ` Marc Zyngier
2023-07-27 12:40 ` Marc Zyngier
2023-07-27 12:40 ` Marc Zyngier
2023-07-31 17:45 ` Raghavendra Rao Ananta
2023-07-31 17:45 ` Raghavendra Rao Ananta
2023-07-31 17:45 ` Raghavendra Rao Ananta
2023-07-31 17:45 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` [PATCH v7 08/12] KVM: arm64: Define kvm_tlb_flush_vmid_range() Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-27 12:47 ` Marc Zyngier
2023-07-27 12:47 ` Marc Zyngier
2023-07-27 12:47 ` Marc Zyngier
2023-07-27 12:47 ` Marc Zyngier
2023-07-27 13:01 ` Marc Zyngier
2023-07-27 13:01 ` Marc Zyngier
2023-07-27 13:01 ` Marc Zyngier
2023-07-27 13:01 ` Marc Zyngier
2023-07-31 18:01 ` Raghavendra Rao Ananta
2023-07-31 18:01 ` Raghavendra Rao Ananta
2023-07-31 18:01 ` Raghavendra Rao Ananta
2023-07-31 18:01 ` Raghavendra Rao Ananta
2023-08-02 23:25 ` Marc Zyngier
2023-08-02 23:25 ` Marc Zyngier
2023-08-02 23:25 ` Marc Zyngier
2023-08-02 23:25 ` Marc Zyngier
2023-07-22 2:22 ` [PATCH v7 09/12] KVM: arm64: Implement kvm_arch_flush_remote_tlbs_range() Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-27 12:48 ` Marc Zyngier
2023-07-27 12:48 ` Marc Zyngier
2023-07-27 12:48 ` Marc Zyngier
2023-07-27 12:48 ` Marc Zyngier
2023-07-22 2:22 ` [PATCH v7 10/12] KVM: arm64: Flush only the memslot after write-protect Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` [PATCH v7 11/12] KVM: arm64: Invalidate the table entries upon a range Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` [PATCH v7 12/12] KVM: arm64: Use TLBI range-based intructions for unmap Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-22 2:22 ` Raghavendra Rao Ananta
2023-07-24 9:34 ` Shaoqin Huang
2023-07-24 9:34 ` Shaoqin Huang
2023-07-24 9:34 ` Shaoqin Huang
2023-07-24 16:47 ` Raghavendra Rao Ananta
2023-07-24 16:47 ` Raghavendra Rao Ananta
2023-07-24 16:47 ` Raghavendra Rao Ananta
2023-07-25 2:32 ` Shaoqin Huang
2023-07-25 2:32 ` Shaoqin Huang
2023-07-25 2:32 ` Shaoqin Huang
2023-07-25 17:23 ` Raghavendra Rao Ananta
2023-07-25 17:23 ` Raghavendra Rao Ananta
2023-07-25 17:23 ` Raghavendra Rao Ananta
2023-07-26 4:06 ` Shaoqin Huang
2023-07-26 4:06 ` Shaoqin Huang
2023-07-26 4:06 ` Shaoqin Huang
2023-07-27 13:12 ` Marc Zyngier
2023-07-27 13:12 ` Marc Zyngier
2023-07-27 13:12 ` Marc Zyngier
2023-07-27 13:12 ` Marc Zyngier
2023-07-31 18:26 ` Raghavendra Rao Ananta
2023-07-31 18:26 ` Raghavendra Rao Ananta
2023-07-31 18:26 ` Raghavendra Rao Ananta
2023-07-31 18:26 ` Raghavendra Rao Ananta
2023-08-02 23:28 ` Marc Zyngier
2023-08-02 23:28 ` Marc Zyngier
2023-08-02 23:28 ` Marc Zyngier
2023-08-02 23:28 ` Marc Zyngier
2023-08-02 23:33 ` Raghavendra Rao Ananta
2023-08-02 23:33 ` Raghavendra Rao Ananta
2023-08-02 23:33 ` Raghavendra Rao Ananta
2023-08-02 23:33 ` Raghavendra Rao Ananta
2023-07-31 21:57 ` [PATCH v7 00/12] KVM: arm64: Add support for FEAT_TLBIRANGE Sean Christopherson
2023-07-31 21:57 ` Sean Christopherson
2023-07-31 21:57 ` Sean Christopherson
2023-07-31 21:57 ` Sean Christopherson
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=ZMgtwp/YCZciRvdr@google.com \
--to=seanjc@google.com \
--cc=kvm-riscv@lists.infradead.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.