From: Oliver Upton <oliver.upton@linux.dev>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.linux.dev,
Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Kunkun Jiang <jiangkunkun@huawei.com>
Subject: [GIT PULL] KVM/arm64 fixes for 6.7, take #1
Date: Sat, 2 Dec 2023 13:18:58 -0800 [thread overview]
Message-ID: <ZWufQneeJiBJLnPb@thinky-boi> (raw)
Hi Paolo,
Here's the first set of fixes for 6.7. There hasn't been very many
interesting issues that have come up this cycle, so it is only a single
patch this time around.
Please pull :)
--
Thanks,
Oliver
The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:
Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-6.7-1
for you to fetch changes up to 8e4ece6889a5b1836b6a135827ac831a5350602a:
KVM: arm64: GICv4: Do not perform a map to a mapped vLPI (2023-11-20 19:13:32 +0000)
----------------------------------------------------------------
KVM/arm64 fixes for 6.7, take #1
- Avoid mapping vLPIs that have already been mapped
----------------------------------------------------------------
Kunkun Jiang (1):
KVM: arm64: GICv4: Do not perform a map to a mapped vLPI
arch/arm64/kvm/vgic/vgic-v4.c | 4 ++++
1 file changed, 4 insertions(+)
next reply other threads:[~2023-12-02 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 21:18 Oliver Upton [this message]
2023-12-08 18:12 ` [GIT PULL] KVM/arm64 fixes for 6.7, take #1 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=ZWufQneeJiBJLnPb@thinky-boi \
--to=oliver.upton@linux.dev \
--cc=james.morse@arm.com \
--cc=jiangkunkun@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox