From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LzaWi-00044u-Jh for qemu-devel@nongnu.org; Thu, 30 Apr 2009 13:58:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LzaWc-00043V-U5 for qemu-devel@nongnu.org; Thu, 30 Apr 2009 13:58:27 -0400 Received: from [199.232.76.173] (port=55125 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LzaWc-00043O-MB for qemu-devel@nongnu.org; Thu, 30 Apr 2009 13:58:22 -0400 Received: from mx2.redhat.com ([66.187.237.31]:35916) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LzaWc-0004ff-5f for qemu-devel@nongnu.org; Thu, 30 Apr 2009 13:58:22 -0400 Message-ID: <49F9E647.8030007@redhat.com> Date: Thu, 30 Apr 2009 20:56:23 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] [RFC] cleanup cpu-exec.c: consolidate handle_cpu_signal References: <1240364008-7065-1-git-send-email-froydnj@codesourcery.com> <200904301710.38740.paul@codesourcery.com> <49F9D329.3030008@redhat.com> <200904301807.36073.paul@codesourcery.com> In-Reply-To: <200904301807.36073.paul@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: qemu-devel@nongnu.org, Nathan Froyd Paul Brook wrote: >> I'd really like to see kvm used to implement something like this (to >> emulate non-x86 on x86). >> > > It's something I've considered a few times. It gets hairy fairly quickly > though. You're probably also going to hit a world of pain if your host > pagesize is larger than your guest pagesize, Yes. But realistically your host is going to be either x86 or x86 (in a few corner cases that no one cares about, x86). Are there targets with page size < 4K? We don't target VAX. > and for guests with a software > managed TLB shadow paging gets much more interesting. > Hmm, inserting a tlb entry would just create x86 page table entries, no? > There's very little of the old code left, and it's bitrotten enough that > there's no point trying to keep it on the offchance that it'll be useful. > Sure, starting from scratch sounds much better, this is going to be wildly different. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.