[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87eea2c9zu.wl-maz@kernel.org>
Date: Mon, 06 Sep 2021 10:46:13 +0100
From: Marc Zyngier <maz@...nel.org>
To: Juergen Gross <jgross@...e.com>
Cc: kvm@...r.kernel.org, x86@...nel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
ehabkost@...hat.com, James Morse <james.morse@....com>,
Alexandru Elisei <alexandru.elisei@....com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Sean Christopherson <seanjc@...gle.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
Joerg Roedel <joro@...tes.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>, kvmarm@...ts.cs.columbia.edu
Subject: Re: [PATCH v2 5/6] kvm: allocate vcpu pointer array separately
On Mon, 06 Sep 2021 05:33:35 +0100,
Juergen Gross <jgross@...e.com> wrote:
>
> On 03.09.21 16:41, Marc Zyngier wrote:
>
> > At this stage, I really wonder why we are not using an xarray instead.
> >
> > I wrote this [1] a while ago, and nothing caught fire. It was also a
> > net deletion of code...
>
> Indeed, I'd prefer that solution!
>
> Are you fine with me swapping my patch with yours in the series?
Of course, feel free to grab the whole series. You'll probably need
the initial patches to set the scene for this. On their own, they are
a nice cleanup, and I trust you can write a decent commit message for
the three patches affecting mips/s390/x86.
I would normally do that myself, but my network connectivity is
reduced to almost nothing at the moment.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists