All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Alexandru Elisei <alexandru.elisei@arm.com>
Cc: kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] KVM/arm64: Don't emulate a PMU for 32-bit guests if feature not set
Date: Wed, 27 Apr 2022 22:10:01 +0100	[thread overview]
Message-ID: <87y1zq8c7q.wl-maz@kernel.org> (raw)
In-Reply-To: <YmkQw8UGFOTFlI1q@monolith.localdoman>

On Wed, 27 Apr 2022 10:45:39 +0100,
Alexandru Elisei <alexandru.elisei@arm.com> wrote:
> 
> Hi,
> 
> On Wed, Apr 27, 2022 at 12:57:57AM -0700, Oliver Upton wrote:
> > Hi Alex,
> > 
> > Seems to me all the AArch32 feature register trap logic should come
> > later on as there's a nonzero chance I introduced a bug :) Shall we
> > stop the bleeding w/ your originally proposed patch? Doesn't seem any
> > more objectionable than what we're already doing.
> 
> I am leaning towards merging this patch to prevent people from seeing the
> splat, and when the AArch32 ID reg series gets merged it can be reverted.
> But in the end it's up to Marc to decide what he prefers.

Yeah, I'd like to plug this ASAP. I'll queue the workaround for 5.18,
and we can rework that the proper way for 5.19.

Thanks to both for working on it together, much appreciated.

	M.

-- 
Without deviation from the norm, progress is not possible.
_______________________________________________
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: Marc Zyngier <maz@kernel.org>
To: Alexandru Elisei <alexandru.elisei@arm.com>
Cc: Oliver Upton <oupton@google.com>,
	james.morse@arm.com, suzuki.poulose@arm.com,
	linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH] KVM/arm64: Don't emulate a PMU for 32-bit guests if feature not set
Date: Wed, 27 Apr 2022 22:10:01 +0100	[thread overview]
Message-ID: <87y1zq8c7q.wl-maz@kernel.org> (raw)
In-Reply-To: <YmkQw8UGFOTFlI1q@monolith.localdoman>

On Wed, 27 Apr 2022 10:45:39 +0100,
Alexandru Elisei <alexandru.elisei@arm.com> wrote:
> 
> Hi,
> 
> On Wed, Apr 27, 2022 at 12:57:57AM -0700, Oliver Upton wrote:
> > Hi Alex,
> > 
> > Seems to me all the AArch32 feature register trap logic should come
> > later on as there's a nonzero chance I introduced a bug :) Shall we
> > stop the bleeding w/ your originally proposed patch? Doesn't seem any
> > more objectionable than what we're already doing.
> 
> I am leaning towards merging this patch to prevent people from seeing the
> splat, and when the AArch32 ID reg series gets merged it can be reverted.
> But in the end it's up to Marc to decide what he prefers.

Yeah, I'd like to plug this ASAP. I'll queue the workaround for 5.18,
and we can rework that the proper way for 5.19.

Thanks to both for working on it together, much appreciated.

	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

  reply	other threads:[~2022-04-27 21:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 14:55 [PATCH] KVM/arm64: Don't emulate a PMU for 32-bit guests if feature not set Alexandru Elisei
2022-04-25 14:55 ` Alexandru Elisei
2022-04-25 17:14 ` Marc Zyngier
2022-04-25 17:14   ` Marc Zyngier
2022-04-25 17:26   ` Oliver Upton
2022-04-25 17:26     ` Oliver Upton
2022-04-26  9:30   ` Alexandru Elisei
2022-04-26  9:30     ` Alexandru Elisei
2022-04-26  8:05 ` Oliver Upton
2022-04-26  8:05   ` Oliver Upton
2022-04-26  9:01   ` Alexandru Elisei
2022-04-26  9:01     ` Alexandru Elisei
2022-04-27  7:57     ` Oliver Upton
2022-04-27  7:57       ` Oliver Upton
2022-04-27  9:45       ` Alexandru Elisei
2022-04-27  9:45         ` Alexandru Elisei
2022-04-27 21:10         ` Marc Zyngier [this message]
2022-04-27 21:10           ` Marc Zyngier
2022-04-28 19:58 ` Marc Zyngier
2022-04-28 19:58   ` 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=87y1zq8c7q.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=alexandru.elisei@arm.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@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.