All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Gavin Shan <gshan@redhat.com>,
	Mostafa Saleh <smostafa@google.com>,
	Oliver Upton <oliver.upton@linux.dev>,
	Quentin Perret <qperret@google.com>,
	Raghavendra Rao Ananta <rananta@google.com>,
	Ryan Roberts <ryan.roberts@arm.com>,
	Shaoqin Huang <shahuang@redhat.com>
Subject: Re: [PATCH v2 0/4] KVM: arm64: TLBI fixes for the pgtable code
Date: Sat, 30 Mar 2024 10:00:29 +0000	[thread overview]
Message-ID: <87sf08rqde.wl-maz@kernel.org> (raw)
In-Reply-To: <20240327124853.11206-1-will@kernel.org>

On Wed, 27 Mar 2024 12:48:49 +0000,
Will Deacon <will@kernel.org> wrote:
> 
> Hi again,
> 
> This is version two of the series I previously posted on Monday:
> 
>   https://lore.kernel.org/r/20240325185158.8565-1-will@kernel.org
> 
> We've got a long weekend coming up in the UK, so I wanted to get this
> out before I chuck the laptop in the river.
> 
> Changes since v1 include:
> 
>   * Add Ryan's Reviewed-by on the third patch
>   * Add an extra patch to ensure correct alignment of range TLBI address
>     argument
>   * Tweak commit messages

For the series,

Reviewed-by: Marc Zyngier <maz@kernel.org>

	M.

-- 
Without deviation from the norm, progress is not possible.

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Gavin Shan <gshan@redhat.com>,
	Mostafa Saleh <smostafa@google.com>,
	Oliver Upton <oliver.upton@linux.dev>,
	Quentin Perret <qperret@google.com>,
	Raghavendra Rao Ananta <rananta@google.com>,
	Ryan Roberts <ryan.roberts@arm.com>,
	Shaoqin Huang <shahuang@redhat.com>
Subject: Re: [PATCH v2 0/4] KVM: arm64: TLBI fixes for the pgtable code
Date: Sat, 30 Mar 2024 10:00:29 +0000	[thread overview]
Message-ID: <87sf08rqde.wl-maz@kernel.org> (raw)
In-Reply-To: <20240327124853.11206-1-will@kernel.org>

On Wed, 27 Mar 2024 12:48:49 +0000,
Will Deacon <will@kernel.org> wrote:
> 
> Hi again,
> 
> This is version two of the series I previously posted on Monday:
> 
>   https://lore.kernel.org/r/20240325185158.8565-1-will@kernel.org
> 
> We've got a long weekend coming up in the UK, so I wanted to get this
> out before I chuck the laptop in the river.
> 
> Changes since v1 include:
> 
>   * Add Ryan's Reviewed-by on the third patch
>   * Add an extra patch to ensure correct alignment of range TLBI address
>     argument
>   * Tweak commit messages

For the series,

Reviewed-by: Marc Zyngier <maz@kernel.org>

	M.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2024-03-30 10:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27 12:48 [PATCH v2 0/4] KVM: arm64: TLBI fixes for the pgtable code Will Deacon
2024-03-27 12:48 ` Will Deacon
2024-03-27 12:48 ` [PATCH v2 1/4] KVM: arm64: Don't defer TLB invalidation when zapping table entries Will Deacon
2024-03-27 12:48   ` Will Deacon
2024-03-27 12:48 ` [PATCH v2 2/4] KVM: arm64: Don't pass a TLBI level hint " Will Deacon
2024-03-27 12:48   ` Will Deacon
2024-03-27 12:48 ` [PATCH v2 3/4] KVM: arm64: Use TLBI_TTL_UNKNOWN in __kvm_tlb_flush_vmid_range() Will Deacon
2024-03-27 12:48   ` Will Deacon
2024-03-27 12:48 ` [PATCH v2 4/4] KVM: arm64: Ensure target address is granule-aligned for range TLBI Will Deacon
2024-03-27 12:48   ` Will Deacon
2024-03-30 10:00 ` Marc Zyngier [this message]
2024-03-30 10:00   ` [PATCH v2 0/4] KVM: arm64: TLBI fixes for the pgtable code Marc Zyngier
2024-04-01  2:57 ` Shaoqin Huang
2024-04-01  2:57   ` Shaoqin Huang
2024-04-01  8:46 ` Oliver Upton
2024-04-01  8:46   ` Oliver Upton

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=87sf08rqde.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=gshan@redhat.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=oliver.upton@linux.dev \
    --cc=qperret@google.com \
    --cc=rananta@google.com \
    --cc=ryan.roberts@arm.com \
    --cc=shahuang@redhat.com \
    --cc=smostafa@google.com \
    --cc=will@kernel.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.