From: Oliver Upton <oliver.upton@linux.dev>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Marc Zyngier" <maz@kernel.org>,
"Andrew Jones" <andrew.jones@linux.dev>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Anshuman Khandual" <anshuman.khandual@arm.com>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Bagas Sanjaya" <bagasdotme@gmail.com>,
"Ben Gardon" <bgardon@google.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Fuad Tabba" <tabba@google.com>, "Gavin Shan" <gshan@redhat.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"James Morse" <james.morse@arm.com>,
"Maciej S . Szmigiero" <maciej.szmigiero@oracle.com>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Mark Brown" <broonie@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Peter Collingbourne" <pcc@google.com>,
"Peter Xu" <peterx@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Quentin Perret" <qperret@google.com>,
"Reiji Watanabe" <reijiw@google.com>,
"Ricardo Koller" <ricarkol@google.com>,
"Ryan Roberts" <ryan.roberts@arm.com>,
"Sean Christopherson" <seanjc@google.com>,
"Steven Price" <steven.price@arm.com>,
"Usama Arif" <usama.arif@bytedance.com>,
"Vincent Donnefort" <vdonnefort@google.com>,
"Will Deacon" <will@kernel.org>,
"Zhiyuan Dai" <daizhiyuan@phytium.com.cn>,
"Suzuki K Poulose" <suzuki.poulose@arm.com>,
"Alexandru Elisei" <alexandru.elisei@arm.com>,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvmarm@lists.linux.dev,
kvm@vger.kernel.org
Subject: Re: [GIT PULL] KVM/arm64 updates for 6.2
Date: Fri, 9 Dec 2022 17:05:21 +0000 [thread overview]
Message-ID: <Y5Nq0a2JxUP+JuP+@google.com> (raw)
In-Reply-To: <5e51cf73-5d51-835f-8748-7554a65d9111@redhat.com>
Hey Paolo,
On Fri, Dec 09, 2022 at 05:56:50PM +0100, Paolo Bonzini wrote:
> On 12/7/22 22:51, Oliver Upton wrote:
> > >
> > > I haven't pushed to kvm/next yet to give you time to check, so the
> > > merge is currently in kvm/queue only.
> > Have a look at this series, which gets things building and actually
> > passing again:
> >
> > https://lore.kernel.org/kvm/20221207214809.489070-1-oliver.upton@linux.dev/
>
> Thank you! Squashed 1-2 and applied 3-4.
I actually wound up sending a v2 for this :)
1-2 are the same, but I addressed some of Sean's feedback and also
pulled in more fixes. In addition to the problems with page_fault_test,
other KVM selftests were magically failing on arm64 because identity
mapping ucall MMIO punched a hole straight through the program image.
Mind dumping what I had in v1 and applying this instead?
https://lore.kernel.org/kvm/20221209015307.1781352-1-oliver.upton@linux.dev/
Thanks!
--
Best,
Oliver
next prev parent reply other threads:[~2022-12-09 17:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 15:58 [GIT PULL] KVM/arm64 updates for 6.2 Marc Zyngier
2022-12-06 17:41 ` Paolo Bonzini
2022-12-06 18:10 ` Sean Christopherson
2022-12-06 18:20 ` Mark Brown
2022-12-06 21:43 ` Paolo Bonzini
2022-12-07 7:49 ` Marc Zyngier
2022-12-09 8:08 ` Paolo Bonzini
2022-12-06 19:27 ` Marc Zyngier
2022-12-07 21:51 ` Oliver Upton
2022-12-09 16:56 ` Paolo Bonzini
2022-12-09 17:05 ` Oliver Upton [this message]
2022-12-09 17:07 ` 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=Y5Nq0a2JxUP+JuP+@google.com \
--to=oliver.upton@linux.dev \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexandru.elisei@arm.com \
--cc=andrew.jones@linux.dev \
--cc=anshuman.khandual@arm.com \
--cc=bagasdotme@gmail.com \
--cc=bgardon@google.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cohuck@redhat.com \
--cc=daizhiyuan@phytium.com.cn \
--cc=gshan@redhat.com \
--cc=james.morse@arm.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=m.szyprowski@samsung.com \
--cc=maciej.szmigiero@oracle.com \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=pcc@google.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qperret@google.com \
--cc=reijiw@google.com \
--cc=ricarkol@google.com \
--cc=ryan.roberts@arm.com \
--cc=seanjc@google.com \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=usama.arif@bytedance.com \
--cc=vdonnefort@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox