From: "Blue Swirl" <blauwirbel@gmail.com>
To: amateur <tianlei.zhao@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] CPUTLBEntry Question
Date: Thu, 14 Jun 2007 17:00:32 +0300 [thread overview]
Message-ID: <f43fc5580706140700p43bc3e30i81e8e2f529b90b32@mail.gmail.com> (raw)
In-Reply-To: <20070614134136.GA6825@163.com>
On 6/14/07, amateur <tianlei.zhao@gmail.com> wrote:
> The softmmu_header.h code does assume each TLB entry has a fixed size
> of (2^CPU_TLB_ENTRY_BITS) bytes. Not only the assembly code, but also
> the C code assume this. So if you want to add new members into
> CPUTLBEntry, add the new member at the end of the data structure, and
> adjust CPU_TLB_ENTRY_BITS accordingly.
No, on Sparc32 target_ulong is 32 bits (on 32-bit host) but
target_phys_addr_t is 64 bits. That makes the structure size 20 bytes.
Everything still works.
next prev parent reply other threads:[~2007-06-14 14:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 20:25 [Qemu-devel] CPUTLBEntry Question Ryan Riley
2007-06-14 13:22 ` Paul Brook
2007-06-14 19:31 ` Ryan Riley
2007-06-14 13:41 ` amateur
2007-06-14 14:00 ` Blue Swirl [this message]
2007-06-15 1:47 ` amateur
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=f43fc5580706140700p43bc3e30i81e8e2f529b90b32@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=tianlei.zhao@gmail.com \
/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).