public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Upton <oliver.upton@linux.dev>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Marc Zyngier <maz@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Will Deacon <will@kernel.org>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [GIT PULL] KVM changes for Linux 6.9 merge window
Date: Fri, 15 Mar 2024 23:49:57 +0000	[thread overview]
Message-ID: <ZfTepXx_lsriEg5U@linux.dev> (raw)
In-Reply-To: <ZfTadCKIL7Ujxw3f@linux.dev>

On Fri, Mar 15, 2024 at 04:32:10PM -0700, Oliver Upton wrote:
> On Fri, Mar 15, 2024 at 03:28:29PM -0700, Linus Torvalds wrote:
> > The immediate cause of the failure is commit b80b701d5a67 ("KVM:
> > arm64: Snapshot all non-zero RES0/RES1 sysreg fields for later
> > checking") but I hope it worked at *some* point. I can't see how.
> 
> Looks like commit fdd867fe9b32 ("arm64/sysreg: Add register fields for
> ID_AA64DFR1_EL1") changed the register definition that tripped the
> BUILD_BUG_ON().
> 
> But it'd be *wildly* unfair to blame that, the KVM assertions are added
> out of fear of new register definitions breaking our sysreg emulation.
> 
> > I would guess / assume that commit cfc680bb04c5 ("arm64: sysreg: Add
> > layout for ID_AA64MMFR4_EL1") is also involved, but having recoiled in
> > horror from the awk script, I really can't even begin to guess at what
> > is going on.
> > 
> > Bringing in other people who hopefully can sort this out.
> 
> At this point I'm heavily biased towards just dropping the KVM checks
> for now than attempt a fix-forward. We can work things out better with
> arm64 folks next release.
> 
> So unless anyone screams, I say we revert:
> 
>   99101dda29e3 ("KVM: arm64: Make build-time check of RES0/RES1 bits optional")
>   891766581dea ("KVM: arm64: Add debugfs file for guest's ID registers")

Duh, that second one should actually be:

  b80b701d5a67 ("KVM: arm64: Snapshot all non-zero RES0/RES1 sysreg fields for later checking")

-- 
Thanks,
Oliver

  reply	other threads:[~2024-03-15 23:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15 17:49 [GIT PULL] KVM changes for Linux 6.9 merge window Paolo Bonzini
2024-03-15 20:37 ` pr-tracker-bot
2024-03-15 22:28 ` Linus Torvalds
2024-03-15 23:32   ` Oliver Upton
2024-03-15 23:49     ` Oliver Upton [this message]
2024-03-16  8:48       ` Paolo Bonzini
2024-03-16 16:01         ` Linus Torvalds
2024-03-17 10:36           ` Marc Zyngier
     [not found]             ` <32892705-1A39-430A-9553-DBF254C723E7@redhat.com>
2024-03-17 13:42               ` Paolo Bonzini
2024-03-16  0:24   ` [PATCH] Revert "KVM: arm64: Snapshot all non-zero RES0/RES1 sysreg fields for later checking" Oliver Upton
2024-03-16  0:51     ` Linus Torvalds
2024-03-16  4:49   ` [GIT PULL] KVM changes for Linux 6.9 merge window Stephen Rothwell

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=ZfTepXx_lsriEg5U@linux.dev \
    --to=oliver.upton@linux.dev \
    --cc=catalin.marinas@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=torvalds@linux-foundation.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