From: Oliver Upton <oliver.upton@linux.dev>
To: Raghavendra Rao Ananta <rananta@google.com>
Cc: Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Jing Zhang <jingzhangos@google.com>,
Colton Lewis <coltonlewis@google.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH v5 0/7] KVM: arm64: Add support for FEAT_TLBIRANGE
Date: Wed, 14 Jun 2023 12:19:16 +0000 [thread overview]
Message-ID: <ZImwRAuSXcVt3UPV@linux.dev> (raw)
In-Reply-To: <20230606192858.3600174-1-rananta@google.com>
Hi Raghavendra,
On Tue, Jun 06, 2023 at 07:28:51PM +0000, Raghavendra Rao Ananta wrote:
> The series is based off of upstream v6.4-rc2, and applied David
> Matlack's common API for TLB invalidations[1] on top.
Sorry I didn't spot the dependency earlier, but this isn't helpful TBH.
David's series was partially applied, and what remains no longer cleanly
applies to the base you suggest. Independent of that, my *strong*
preference is that you just send out a series containing your patches as
well as David's. Coordinating dependent efforts is the only sane thing
to do. Also, those patches are 5 months old at this point which is
ancient history.
> [1]:
> https://lore.kernel.org/linux-arm-kernel/20230126184025.2294823-1-dmatlack@google.com/
--
Thanks,
Oliver
WARNING: multiple messages have this Message-ID (diff)
From: Oliver Upton <oliver.upton@linux.dev>
To: Raghavendra Rao Ananta <rananta@google.com>
Cc: Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Jing Zhang <jingzhangos@google.com>,
Colton Lewis <coltonlewis@google.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH v5 0/7] KVM: arm64: Add support for FEAT_TLBIRANGE
Date: Wed, 14 Jun 2023 12:19:16 +0000 [thread overview]
Message-ID: <ZImwRAuSXcVt3UPV@linux.dev> (raw)
In-Reply-To: <20230606192858.3600174-1-rananta@google.com>
Hi Raghavendra,
On Tue, Jun 06, 2023 at 07:28:51PM +0000, Raghavendra Rao Ananta wrote:
> The series is based off of upstream v6.4-rc2, and applied David
> Matlack's common API for TLB invalidations[1] on top.
Sorry I didn't spot the dependency earlier, but this isn't helpful TBH.
David's series was partially applied, and what remains no longer cleanly
applies to the base you suggest. Independent of that, my *strong*
preference is that you just send out a series containing your patches as
well as David's. Coordinating dependent efforts is the only sane thing
to do. Also, those patches are 5 months old at this point which is
ancient history.
> [1]:
> https://lore.kernel.org/linux-arm-kernel/20230126184025.2294823-1-dmatlack@google.com/
--
Thanks,
Oliver
_______________________________________________
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-06-14 12:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 19:28 [PATCH v5 0/7] KVM: arm64: Add support for FEAT_TLBIRANGE Raghavendra Rao Ananta
2023-06-06 19:28 ` Raghavendra Rao Ananta
2023-06-06 19:28 ` [PATCH v5 1/7] arm64: tlb: Refactor the core flush algorithm of __flush_tlb_range Raghavendra Rao Ananta
2023-06-06 19:28 ` Raghavendra Rao Ananta
2023-06-06 19:28 ` [PATCH v5 2/7] KVM: arm64: Implement __kvm_tlb_flush_vmid_range() Raghavendra Rao Ananta
2023-06-06 19:28 ` Raghavendra Rao Ananta
2023-06-06 19:28 ` [PATCH v5 3/7] KVM: arm64: Define kvm_tlb_flush_vmid_range() Raghavendra Rao Ananta
2023-06-06 19:28 ` Raghavendra Rao Ananta
2023-06-06 19:28 ` [PATCH v5 4/7] KVM: arm64: Implement kvm_arch_flush_remote_tlbs_range() Raghavendra Rao Ananta
2023-06-06 19:28 ` Raghavendra Rao Ananta
2023-06-06 19:28 ` [PATCH v5 5/7] KVM: arm64: Flush only the memslot after write-protect Raghavendra Rao Ananta
2023-06-06 19:28 ` Raghavendra Rao Ananta
2023-06-06 19:28 ` [PATCH v5 6/7] KVM: arm64: Invalidate the table entries upon a range Raghavendra Rao Ananta
2023-06-06 19:28 ` Raghavendra Rao Ananta
2023-06-06 19:28 ` [PATCH v5 7/7] KVM: arm64: Use TLBI range-based intructions for unmap Raghavendra Rao Ananta
2023-06-06 19:28 ` Raghavendra Rao Ananta
2023-06-14 12:19 ` Oliver Upton [this message]
2023-06-14 12:19 ` [PATCH v5 0/7] KVM: arm64: Add support for FEAT_TLBIRANGE Oliver Upton
2023-06-15 1:57 ` Raghavendra Rao Ananta
2023-06-15 1:57 ` Raghavendra Rao Ananta
2023-06-15 8:39 ` Oliver Upton
2023-06-15 8:39 ` Oliver Upton
2023-06-15 14:14 ` Sean Christopherson
2023-06-15 14:14 ` Sean Christopherson
2023-06-15 17:26 ` Raghavendra Rao Ananta
2023-06-15 17:26 ` Raghavendra Rao Ananta
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=ZImwRAuSXcVt3UPV@linux.dev \
--to=oliver.upton@linux.dev \
--cc=coltonlewis@google.com \
--cc=james.morse@arm.com \
--cc=jingzhangos@google.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=rananta@google.com \
--cc=suzuki.poulose@arm.com \
/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.