All of lore.kernel.org
 help / color / mirror / Atom feed
From: Torbjorn Granlund <tg@gmplib.org>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Which qemu ports actually work?
Date: Thu, 28 Oct 2010 10:32:38 +0200	[thread overview]
Message-ID: <868w1i4t09.fsf@shell.gmplib.org> (raw)
In-Reply-To: <55EA6A25-A935-4FFE-A610-D40E9E6F787A@suse.de> (Alexander Graf's message of "Wed\, 27 Oct 2010 01\:51\:25 -0700")

Alexander Graf <agraf@suse.de> writes:

  >  Please also keep in mind that PPC emulation is _very_ slow.
  > 
  > Why is it slow?
  
  Because we're flushing the TLB on almost every MMU opcode.

OK.  Does that mean the TLB never gets more than a single entry?
(I mean, do you flush the TLB before inserting a new entry into it?)

What is the reason for this flushing?

A related thing, related to cross endianess: I wrote a simulator many
years ago (around 1990) that turned memory "upside down" for cross
endianess.  I.e., a reference to address x was simulated as
*(memend-opsize-x), where memend points to the end of the area
simulating memory, opsize of the size in bytes of the operation.

The point of this is that one can use full-size native load or store
instructions, instead of many byte operations and shifts.

I never published this idea, but I assume it has been rediscovered and
is now a standard trick?

[Alex, excuse the duplicate, this message was bounced by nongnu.org's
MTA for bogus reasons.  It never appeared on the list.]

-- 
Torbjörn

  parent reply	other threads:[~2010-10-28  8:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26 16:38 [Qemu-devel] Which qemu ports actually work? Torbjorn Granlund
2010-10-26 17:13 ` Alexander Graf
2010-10-26 19:02   ` Torbjorn Granlund
2010-10-26 19:25     ` Alexander Graf
2010-10-26 19:52       ` Torbjorn Granlund
2010-10-27  5:06         ` Alexander Graf
2010-10-27  8:39           ` Torbjorn Granlund
2010-10-27  8:51             ` Alexander Graf
2010-10-27  9:21               ` Torbjorn Granlund
2010-10-27  9:24                 ` Alexander Graf
2010-10-27  9:33                   ` Torbjorn Granlund
2010-10-27  9:31                 ` [Qemu-devel] " Paolo Bonzini
2010-10-28  8:32               ` Torbjorn Granlund [this message]
2010-10-28 20:00                 ` [Qemu-devel] " Alexander Graf
2010-10-27 20:44             ` Blue Swirl
2010-10-27 22:39               ` Torbjorn Granlund
2010-10-28  8:57                 ` Artyom Tarasenko
2010-10-28  9:37                   ` Torbjorn Granlund
2010-10-28 10:41                     ` Artyom Tarasenko
2010-10-26 19:34     ` [Qemu-devel] " Paolo Bonzini
2010-10-26 21:02       ` Stefan Weil
2010-10-26 17:53 ` [Qemu-devel] " Stefan Weil
2010-10-26 19:12   ` Torbjorn Granlund
2010-10-26 19:35     ` [Qemu-devel] " Paolo Bonzini
2010-10-26 20:07       ` Torbjorn Granlund
2010-10-26 20:54         ` Stefan Weil
2010-10-26 21:11           ` Torbjorn Granlund
2010-10-26 21:09         ` Paolo Bonzini
2010-10-26 18:19 ` [Qemu-devel] Which qemu targets actually work? (was: Which qemu ports actually work?) Andreas Färber
2010-10-26 18:25 ` [Qemu-devel] Which qemu ports actually work? Blue Swirl

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=868w1i4t09.fsf@shell.gmplib.org \
    --to=tg@gmplib.org \
    --cc=agraf@suse.de \
    --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.