From: "Olivier Cozette" <olivier.cozette@u-picardie.fr>
To: 'Ye Wen' <wen@umail.ucsb.edu>
Cc: qemu-devel@nongnu.org
Subject: RE : Another related question Re: [Qemu-devel] Question about softmmu
Date: Fri, 12 Nov 2004 18:30:52 +0100 [thread overview]
Message-ID: <002e01c4c8dd$5b7cce10$f618100a@Olivier> (raw)
In-Reply-To: <1100161300.41932114cac38@webaccess.umail.ucsb.edu>
I Ye,
I understand your problem, but in this case, you must change the mapping and
so you must send this change to the processor (access special memory,
explicitly invalidate one page), so the page is flushed
(tlb_flush_page/exec.c) and all tb in this page are invalidate
(tb_invalidate/exec.c). So tb_invalidate delete all tb that call this tb.
This function deletes all jmp to this tb.
So, in my opinion, you problem won't occur.
Olivier
>Actually I'm thinking of a special case:
>1. A basic block is translated and the PC value patched in is
> the virtual address when it is translated. At this time,
> the address mapping is virtual page 0 -> physical page 0
>2. Now the mapping changes. virtual page 1 -> physical page 0,
> which means the physical location of the block doesn't change
> but its virtual address changes.
>3. Since page table changes, the virtual pc hash flushed. But we
> still can find the block using physical hash.
>4. Now the block is executed again. But since the embedded pc value
> is still the old value, will this cause problem?
next prev parent reply other threads:[~2004-11-12 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 14:15 Re:Another related question Re: [Qemu-devel] Question about softmmu olivier cozette
2004-11-11 8:21 ` Ye Wen
2004-11-12 17:30 ` Olivier Cozette [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-10 14:15 olivier cozette
2004-11-09 16:01 Olivier Cozette
2004-11-09 19:33 ` Ye Wen
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='002e01c4c8dd$5b7cce10$f618100a@Olivier' \
--to=olivier.cozette@u-picardie.fr \
--cc=qemu-devel@nongnu.org \
--cc=wen@umail.ucsb.edu \
/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).