From: "Andreas Färber" <afaerber@suse.de>
To: Michael Rolnik <mrolnik@gmail.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] TLB collision
Date: Thu, 24 Nov 2011 11:10:41 +0100 [thread overview]
Message-ID: <4ECE1821.8030106@suse.de> (raw)
In-Reply-To: <CAK4993ic=_h6LO2u9u1X3Ub5ypUr4vx+4N-GrZ78ga_4PnP=ww@mail.gmail.com>
Hi,
Am 24.11.2011 10:53, schrieb Michael Rolnik:
> I have a question regarding MMU.
> I've built a SPARC based small embedded system.
You've already sent this two times. What you keep forgetting is to cc
the sparc maintainer and to tell us whether this is sparc32 or sparc64.
The latter was rather incomplete, so you might be hitting a corner case.
Also when building new machines you are generally well advised to use an
up-to-date git version.
Regards,
Andreas
> at this system addresses 0x00000000-0x00008000 (32KB) belong to ROM and
> 0x80000000 - 0x80010000 to RAM.
> the problem is that when a code from first ROM page accesses a memory at
> the address 0x80000000 there is an infinite loop.
>
> - cpu_sparc_handle_mmu_fault is called to bring addres 0x00000000
> - cpu_sparc_handle_mmu_fault is called to bring 0x80000000 and
> flushes 0x00000000
> - cpu_sparc_handle_mmu_fault is called to bring 0x00000000 and
> flushes 0x80000000
> ...
>
> this can be fixed if I set CPU_TLB_BITS to be 20 bits (assuming page
> size of 4KB).
>
> is there a better solution?
>
>
> I was thinking about 2-way TLB so two virtual addresses sharing same TLB
> entry will be resident.
> in order not to degrade performance
> 1. *tcg_out_qemu_ld* and *tcg_out_qemu_st* should remain as it,
> which mean they will always look into way0.
> 2. *tlb_set_page* should copy way0 to way1 and program way0 with new
> values
> 3. all other routines dealing with TLB should search both ways.
>
> what do you think?
>
> --
> Best Regards,
> Michael Rolnik
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2011-11-24 10:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 9:53 [Qemu-devel] TLB collision Michael Rolnik
2011-11-24 10:10 ` Andreas Färber [this message]
2011-11-26 7:45 ` 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=4ECE1821.8030106@suse.de \
--to=afaerber@suse.de \
--cc=blauwirbel@gmail.com \
--cc=mrolnik@gmail.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.