From: Pavel Hrdina <phrdina@redhat.com>
To: David Gibson <dwg@au1.ibm.com>
Cc: aliguori@us.ibm.com, "Andreas Färber" <afaerber@suse.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] cpu_physical_memory_write_rom() needs to do TB invalidates
Date: Mon, 01 Oct 2012 15:43:45 +0200 [thread overview]
Message-ID: <50699E11.8020203@redhat.com> (raw)
In-Reply-To: <20120912055706.GX12554@truffula.fritz.box>
On 09/12/2012 07:57 AM, David Gibson wrote:
> On Mon, Sep 10, 2012 at 03:27:45PM +0200, Andreas Färber wrote:
>> Am 10.09.2012 04:30, schrieb David Gibson:
>>> 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
>> "doesn't"?
>>
>> Otherwise doesn't look wrong.
> Oops, comment updated.
>
> From 6b913afaf83f52ee787271827c84b492e8ac5895 Mon Sep 17 00:00:00 2001
> From: David Gibson <david@gibson.dropbear.id.au>
> Date: Wed, 22 Aug 2012 14:58:04 +1000
> Subject: [PATCH] cpu_physical_memory_write_rom() needs to do TB invalidates
>
> 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() doesn't 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;
Hi,
this patch breaks Windows XP guest at all. Windows XP boot ends in loob
by restarting itself after time-out expires in windows advanced boot
options.
I started the guest using this command-line:
./x86_64-softmmu/qemu-system-x86_64 -m 2G -drive
file=/data/data-shared/images/winxp-test.img -vnc 0.0.0.0:0
Pavel
next prev parent reply other threads:[~2012-10-01 13:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 2:30 [Qemu-devel] [0/2] Bugfixes for 1.2 stable series David Gibson
2012-09-10 2:30 ` [Qemu-devel] [PATCH 1/2] qemu-char: BUGFIX, don't call FD_ISSET with negative fd David Gibson
2012-09-17 18:24 ` Anthony Liguori
2012-09-18 0:08 ` David Gibson
2012-09-18 11:29 ` Andreas Färber
2012-09-19 0:30 ` David Gibson
2012-09-10 2:30 ` [Qemu-devel] [PATCH 2/2] cpu_physical_memory_write_rom() needs to do TB invalidates David Gibson
2012-09-10 13:27 ` Andreas Färber
2012-09-12 5:57 ` David Gibson
2012-10-01 13:43 ` Pavel Hrdina [this message]
2012-10-01 14:28 ` Anthony Liguori
2012-10-01 15:34 ` Pavel Hrdina
2012-10-01 16:21 ` Anthony Liguori
2012-10-01 16:25 ` Pavel Hrdina
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=50699E11.8020203@redhat.com \
--to=phrdina@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=dwg@au1.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).