[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1342501220-10209-1-git-send-email-michael@ellerman.id.au>
Date: Tue, 17 Jul 2012 15:00:10 +1000
From: Michael Ellerman <michael@...erman.id.au>
To: <kvm@...r.kernel.org>
Cc: <linux-kernel@...r.kernel.org>, <matt@...abs.org>,
<penberg@...nel.org>, <kvm-ppc@...r.kernel.org>,
<prerna@...ux.vnet.ibm.com>,
David Gibson <david@...son.dropbear.id.au>
Subject: [RFC/PATCH] Use kernel supplied MMU info for kvm tool
Hi all,
This is a series for kvmtool that uses a newish kernel API to get
MMU info, which is then fed to the guest.
Currently we just make a good guess based on the PVR, but that is
potentially flakey in a few ways. The most notable is that if you don't
specify hugepages we don't boot - because the guest is told we support
16M pages, but we don't really (on HV).
I've tested this with 4K/64K host page size, and with hugepages, on
both 3.4 and 3.5 based host kernels. I've also given it a quick smoke
test with PR KVM, and it seems to work.
I'm seeing a guest crash with a 4K host kernel, but I think that is
unrelated, and happens with or without this patch series.
cheers
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists