From: James Clark <james.clark@arm.com>
To: kvmarm@lists.linux.dev
Cc: Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
linux-kernel@vger.kernel.org, James Clark <james.clark@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/1] KVM: arm64: PMU: Fix PMCR_EL0 reset value
Date: Fri, 9 Dec 2022 16:44:45 +0000 [thread overview]
Message-ID: <20221209164446.1972014-1-james.clark@arm.com> (raw)
Hi,
We noticed qemu failing to run because of an assert on our CI. I don't see the issue anymore with
this fix.
Applies to kvmarm/next (753d734f3f34)
Thanks
James Clark (1):
KVM: arm64: PMU: Fix PMCR_EL0 reset value
arch/arm64/kvm/sys_regs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.25.1
_______________________________________________
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: James Clark <james.clark@arm.com>
To: kvmarm@lists.linux.dev
Cc: James Clark <james.clark@arm.com>, Marc Zyngier <maz@kernel.org>,
James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] KVM: arm64: PMU: Fix PMCR_EL0 reset value
Date: Fri, 9 Dec 2022 16:44:45 +0000 [thread overview]
Message-ID: <20221209164446.1972014-1-james.clark@arm.com> (raw)
Message-ID: <20221209164445.IU6GmLbhybYYaxSJ3POkJVI2E-q_L1wLcEkcVlzmZ9U@z> (raw)
Hi,
We noticed qemu failing to run because of an assert on our CI. I don't see the issue anymore with
this fix.
Applies to kvmarm/next (753d734f3f34)
Thanks
James Clark (1):
KVM: arm64: PMU: Fix PMCR_EL0 reset value
arch/arm64/kvm/sys_regs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.25.1
next reply other threads:[~2022-12-09 16:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 16:44 James Clark [this message]
2022-12-09 16:44 ` [PATCH 0/1] KVM: arm64: PMU: Fix PMCR_EL0 reset value James Clark
2022-12-09 16:44 ` [PATCH 1/1] " James Clark
2022-12-09 16:44 ` James Clark
2022-12-09 17:58 ` Oliver Upton
2022-12-09 17:58 ` Oliver Upton
2022-12-10 11:16 ` Marc Zyngier
2022-12-10 11:16 ` Marc Zyngier
2022-12-12 6:08 ` Anshuman Khandual
2022-12-12 6:08 ` Anshuman Khandual
2022-12-13 18:22 ` Ricardo Koller
2022-12-13 18:22 ` Ricardo Koller
2022-12-12 9:08 ` [PATCH 0/1] " Marc Zyngier
2022-12-12 9:08 ` Marc Zyngier
2023-01-03 17:57 ` Marc Zyngier
2023-01-03 17:57 ` Marc Zyngier
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=20221209164446.1972014-1-james.clark@arm.com \
--to=james.clark@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox