[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3208be2b-7e9f-413b-a9dc-c36ef4e3d177@amazon.de>
Date: Fri, 4 Oct 2024 12:44:30 +0200
From: Nikolas Wipper <nikwip@...zon.de>
To: Paolo Bonzini <pbonzini@...hat.com>, Sean Christopherson
<seanjc@...gle.com>, Vitaly Kuznetsov <vkuznets@...hat.com>
CC: Nicolas Saenz Julienne <nsaenz@...zon.com>, Alexander Graf
<graf@...zon.de>, James Gowans <jgowans@...zon.com>,
<nh-open-source@...zon.com>, Thomas Gleixner <tglx@...utronix.de>, "Ingo
Molnar" <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>, Dave Hansen
<dave.hansen@...ux.intel.com>, <linux-kernel@...r.kernel.org>,
<kvm@...r.kernel.org>, <x86@...nel.org>, <linux-doc@...r.kernel.org>,
<linux-kselftest@...r.kernel.org>, <kvmarm@...ts.linux.dev>,
<kvm-riscv@...ts.infradead.org>, Nikolas Wipper <nik.wipper@....de>
Subject: Re: [PATCH 00/15] KVM: x86: Introduce new ioctl KVM_TRANSLATE2
I saw this on another series[*]:
> if KVM_TRANSLATE2 lands (though I'm somewhat curious as to why QEMU doesn't do
> the page walks itself).
The simple reason for keeping this functionality in KVM, is that it already
has a mature, production-level page walker (which is already exposed) and
creating something similar QEMU would take a lot longer and would be much
harder to maintain than just creating an API that leverages the existing
walker.
[*] https://lore.kernel.org/lkml/ZvJseVoT7gN_GBG3@google.com/T/#mb0b23a1f5023192a442db4a16629d9ca74eb6b5e
ps: this is also a gentle ping for review, if this got lost in between
conferences
Amazon Web Services Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 257764 B
Sitz: Berlin
Ust-ID: DE 365 538 597
Powered by blists - more mailing lists