qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Clemens Kolbitsch <clemens.kol@gmx.at>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] CPU_TLB_BITS / CPU_TLB_SIZE
Date: Thu, 4 Oct 2007 14:05:22 +0100	[thread overview]
Message-ID: <20071004130522.GT16772@networkno.de> (raw)
In-Reply-To: <200710041438.01463.clemens.kol@gmx.at>

Clemens Kolbitsch wrote:
> hi everyone!
> if i want to increase the size of my TLB (for emulating an i386 processor), is 
> it enough to simply increase CPU_TLB_BITS (e.g. by one)??

IIRC CPU_TLB_BITS needs to be a 2^n value.


Thiemo

  reply	other threads:[~2007-10-04 13:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071003160352.23790gmx1@mx060.gmx.net>
2007-10-04 12:38 ` [Qemu-devel] CPU_TLB_BITS / CPU_TLB_SIZE Clemens Kolbitsch
2007-10-04 13:05   ` Thiemo Seufer [this message]
2007-10-04 13:11     ` Clemens Kolbitsch
2007-10-04 13:46       ` Thiemo Seufer

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=20071004130522.GT16772@networkno.de \
    --to=ths@networkno.de \
    --cc=clemens.kol@gmx.at \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).