From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Joel Stanley" <joel@jms.id.au>,
qemu-block@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
qemu-arm@nongnu.org, jusual@mail.ru,
"Laurent Vivier" <lvivier@redhat.com>,
jim@groklearning.com,
"Peter Crosthwaite" <crosthwaite.peter@gmail.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>, "Max Reitz" <mreitz@redhat.com>,
"Steffen Görtz" <contrib@steffen-goertz.de>,
"Richard Henderson" <rth@twiddle.net>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH v2 2/5] pflash: flush rom device memory region
Date: Wed, 23 Jan 2019 21:22:31 +0000 [thread overview]
Message-ID: <20190123212234.32068-3-stefanha@redhat.com> (raw)
In-Reply-To: <20190123212234.32068-1-stefanha@redhat.com>
pflash devices should mark the memory region dirty and invalidate TBs
after directly writing to the RAM backing the ROM device.
Note that pflash_cfi01_get_memory() is used by several machine types to
populate ROM contents directly. Callers are untouched by this patch
because they only modify memory before the guest is started.
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
hw/block/pflash_cfi01.c | 5 +++++
hw/block/pflash_cfi02.c | 8 ++++++++
2 files changed, 13 insertions(+)
diff --git a/hw/block/pflash_cfi01.c b/hw/block/pflash_cfi01.c
index bffb4c40e7..5301c11c18 100644
--- a/hw/block/pflash_cfi01.c
+++ b/hw/block/pflash_cfi01.c
@@ -446,6 +446,7 @@ static inline void pflash_data_write(pflash_t *pfl, hwaddr offset,
break;
}
+ memory_region_flush_rom_device(&pfl->mem, offset, width);
}
static void pflash_write(pflash_t *pfl, hwaddr offset,
@@ -482,6 +483,8 @@ static void pflash_write(pflash_t *pfl, hwaddr offset,
if (!pfl->ro) {
memset(p + offset, 0xff, pfl->sector_len);
pflash_update(pfl, offset, pfl->sector_len);
+ memory_region_flush_rom_device(&pfl->mem, offset,
+ pfl->sector_len);
} else {
pfl->status |= 0x20; /* Block erase error */
}
@@ -763,6 +766,8 @@ static void pflash_cfi01_realize(DeviceState *dev, Error **errp)
error_setg(errp, "failed to read the initial flash content");
return;
}
+
+ memory_region_flush_rom_device(&pfl->mem, 0, total_len);
}
/* Default to devices being used at their maximum device width. This was
diff --git a/hw/block/pflash_cfi02.c b/hw/block/pflash_cfi02.c
index 0f8b7b8c7b..d04572eca4 100644
--- a/hw/block/pflash_cfi02.c
+++ b/hw/block/pflash_cfi02.c
@@ -378,6 +378,8 @@ static void pflash_write (pflash_t *pfl, hwaddr offset,
pflash_update(pfl, offset, 4);
break;
}
+
+ memory_region_flush_rom_device(&pfl->orig_mem, offset, width);
}
pfl->status = 0x00 | ~(value & 0x80);
/* Let's pretend write is immediate */
@@ -426,6 +428,8 @@ static void pflash_write (pflash_t *pfl, hwaddr offset,
if (!pfl->ro) {
memset(pfl->storage, 0xFF, pfl->chip_len);
pflash_update(pfl, 0, pfl->chip_len);
+ memory_region_flush_rom_device(&pfl->orig_mem, 0,
+ pfl->chip_len);
}
pfl->status = 0x00;
/* Let's wait 5 seconds before chip erase is done */
@@ -441,6 +445,8 @@ static void pflash_write (pflash_t *pfl, hwaddr offset,
if (!pfl->ro) {
memset(p + offset, 0xFF, pfl->sector_len);
pflash_update(pfl, offset, pfl->sector_len);
+ memory_region_flush_rom_device(&pfl->orig_mem, offset,
+ pfl->sector_len);
}
pfl->status = 0x00;
/* Let's wait 1/2 second before sector erase is done */
@@ -590,6 +596,8 @@ static void pflash_cfi02_realize(DeviceState *dev, Error **errp)
error_setg(errp, "failed to read the initial flash content");
return;
}
+
+ memory_region_flush_rom_device(&pfl->orig_mem, 0, chip_len);
}
pflash_setup_mappings(pfl);
--
2.20.1
next prev parent reply other threads:[~2019-01-23 21:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 21:22 [Qemu-devel] [PATCH v2 0/5] arm: microbit Non-Volatile Memory Controller Stefan Hajnoczi
2019-01-23 21:22 ` [Qemu-devel] [PATCH v2 1/5] memory: add memory_region_flush_rom_device() Stefan Hajnoczi
2019-01-23 21:22 ` Stefan Hajnoczi [this message]
2019-01-24 11:11 ` [Qemu-devel] [PATCH v2 2/5] pflash: flush rom device memory region Philippe Mathieu-Daudé
2019-01-25 10:28 ` Stefan Hajnoczi
2019-01-25 10:36 ` Peter Maydell
2019-01-25 15:37 ` Stefan Hajnoczi
2019-01-25 16:00 ` Philippe Mathieu-Daudé
2019-01-23 21:22 ` [Qemu-devel] [PATCH v2 3/5] hw/nvram/nrf51_nvm: Add nRF51 non-volatile memories Stefan Hajnoczi
2019-01-23 21:22 ` [Qemu-devel] [PATCH v2 4/5] arm: Instantiate NRF51 special NVM's and NVMC Stefan Hajnoczi
2019-01-23 21:22 ` [Qemu-devel] [PATCH v2 5/5] tests/microbit-test: Add tests for nRF51 NVMC Stefan Hajnoczi
2019-01-24 9:53 ` Thomas Huth
2019-01-24 13:38 ` [Qemu-devel] [PATCH v2 0/5] arm: microbit Non-Volatile Memory Controller Peter Maydell
2019-01-24 13:58 ` Peter Maydell
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=20190123212234.32068-3-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=contrib@steffen-goertz.de \
--cc=crosthwaite.peter@gmail.com \
--cc=jim@groklearning.com \
--cc=joel@jms.id.au \
--cc=jusual@mail.ru \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.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).