All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org, Nathan Froyd <froydnj@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] [RFC] cleanup cpu-exec.c: consolidate handle_cpu_signal
Date: Thu, 30 Apr 2009 20:56:23 +0300	[thread overview]
Message-ID: <49F9E647.8030007@redhat.com> (raw)
In-Reply-To: <200904301807.36073.paul@codesourcery.com>

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.

  reply	other threads:[~2009-04-30 17:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22  1:33 [Qemu-devel] [PATCH] [RFC] cleanup cpu-exec.c: consolidate handle_cpu_signal Nathan Froyd
2009-04-30 16:10 ` Paul Brook
2009-04-30 16:34   ` Avi Kivity
2009-04-30 17:07     ` Paul Brook
2009-04-30 17:56       ` Avi Kivity [this message]
2009-04-30 18:52         ` Blue Swirl
2009-04-30 18:57           ` Avi Kivity
2009-04-30 19:05             ` Blue Swirl
2009-04-30 20:52           ` Laurent Desnogues
2009-08-01 20:42 ` Filip Navara
2009-08-03 15:59   ` Nathan Froyd

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=49F9E647.8030007@redhat.com \
    --to=avi@redhat.com \
    --cc=froydnj@codesourcery.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.