All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Paul Brook <paul@codesourcery.com>,
	Nathan Froyd <froydnj@codesourcery.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] [RFC] cleanup cpu-exec.c: consolidate handle_cpu_signal
Date: Thu, 30 Apr 2009 21:57:46 +0300	[thread overview]
Message-ID: <49F9F4AA.3060603@redhat.com> (raw)
In-Reply-To: <f43fc5580904301152i3c183d1ftd2961f9e67d39361@mail.gmail.com>

Blue Swirl wrote:
>> 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.
>>     
>
> ARM has 2k pages IIRC.

ARM is one of the most interesting targets, so this is too bad.

>  Sparc64 has 8k pages and then we have the same
> case for x86 target.
>   

There is no kvm for sparc64.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

  reply	other threads:[~2009-04-30 18:59 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
2009-04-30 18:52         ` Blue Swirl
2009-04-30 18:57           ` Avi Kivity [this message]
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=49F9F4AA.3060603@redhat.com \
    --to=avi@redhat.com \
    --cc=blauwirbel@gmail.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.