From: David Gibson <david@gibson.dropbear.id.au>
To: aliguori@us.ibm.com, qemu-devel@nongnu.org
Cc: agraf@suse.de, David Gibson <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [PATCH] cpu_physical_memory_write_rom() needs to do TB invalidates
Date: Wed, 22 Aug 2012 14:59:20 +1000 [thread overview]
Message-ID: <1345611560-8290-1-git-send-email-david@gibson.dropbear.id.au> (raw)
cpu_physical_memory_write_rom(), despite the name, can also be used to
write images into RAM - and will often be used that way if the machine
uses load_image_targphys() into RAM addresses.
However, cpu_physical_memory_write_rom(), unlike cpu_physical_memory_rw()
does invalidate any cached TBs which might be affected by the region
written.
This was breaking reset (under full emu) on the pseries machine - we loaded
our firmware image into RAM, and while executing it rewrite the code at
the entry point (correctly causing a TB invalidate/refresh). When we
reset the firmware image was reloaded, but the TB from the rewrite was
still active and caused us to get an illegal instruction trap.
This patch fixes the bug by duplicating the tb invalidate code from
cpu_physical_memory_rw() in cpu_physical_memory_write_rom().
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
exec.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/exec.c b/exec.c
index 5834766..eff40d7 100644
--- a/exec.c
+++ b/exec.c
@@ -3523,6 +3523,13 @@ void cpu_physical_memory_write_rom(target_phys_addr_t addr,
/* ROM/RAM case */
ptr = qemu_get_ram_ptr(addr1);
memcpy(ptr, buf, l);
+ if (!cpu_physical_memory_is_dirty(addr1)) {
+ /* invalidate code */
+ tb_invalidate_phys_page_range(addr1, addr1 + l, 0);
+ /* set dirty bit */
+ cpu_physical_memory_set_dirty_flags(
+ addr1, (0xff & ~CODE_DIRTY_FLAG));
+ }
qemu_put_ram_ptr(ptr);
}
len -= l;
--
1.7.10.4
next reply other threads:[~2012-08-22 4:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 4:59 David Gibson [this message]
2012-08-22 5:55 ` [Qemu-devel] [PATCH] cpu_physical_memory_write_rom() needs to do TB invalidates Alexander Graf
2012-08-22 5:57 ` David Gibson
2012-08-22 6:02 ` Alexander Graf
2012-08-22 6:10 ` David Gibson
2012-08-22 6:12 ` Alexander Graf
2012-08-22 6:31 ` Alexander Graf
2012-08-22 6:47 ` Jan Kiszka
2012-08-22 7:05 ` Jan Kiszka
2012-08-22 11:38 ` David Gibson
2012-08-22 11:47 ` Alexander Graf
2012-08-22 13:09 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2012-09-03 0:58 David Gibson
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=1345611560-8290-1-git-send-email-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.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 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).