[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-arm] [Qemu-devel] [PATCH v2 2/5] pflash: flush rom device memo
Re: [Qemu-arm] [Qemu-devel] [PATCH v2 2/5] pflash: flush rom device memory region
Fri, 25 Jan 2019 17:00:07 +0100
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
On 1/25/19 4:37 PM, Stefan Hajnoczi wrote:
> On Fri, Jan 25, 2019 at 10:36:17AM +0000, Peter Maydell wrote:
>> On Fri, 25 Jan 2019 at 10:28, Stefan Hajnoczi <address@hidden> wrote:
>>> On Thu, Jan 24, 2019 at 12:11:55PM +0100, Philippe Mathieu-Daudé wrote:
>>>> The device realize() is also executed before the guest is started, is
>>>> this call really necessary?
>>> My rationale was that machine init only happens before the guest is
>>> started while ->realize() is called by hotplug too.
>> Yes, but before realize the flash memory can't actually be
>> visible to the guest, so there's no need to invalidate anything.
>>> That said, can pflash devices be hotplugged?
>> I guess you could have one inside a hotplugged device in theory;
>> they can't be directly hotpluggged. (I bet that in practice
>> there are leaks though if you did do that, and we don't have
>> any devices that do so today.)
Can we assume pflash aren't hotpluggable until someone find an use case
and is willing to work on it? I can't find any practical example.
>>> If you guys prefer not flushing from pflash ->realize() then I'll drop
>> I think it makes more sense not to do a flush in the realize method.
> Okay, I'll resend this patch.
Description: OpenPGP digital signature
[Qemu-arm] [PATCH v2 3/5] hw/nvram/nrf51_nvm: Add nRF51 non-volatile memories, Stefan Hajnoczi, 2019/01/23
[Qemu-arm] [PATCH v2 5/5] tests/microbit-test: Add tests for nRF51 NVMC, Stefan Hajnoczi, 2019/01/23
[Qemu-arm] [PATCH v2 4/5] arm: Instantiate NRF51 special NVM's and NVMC, Stefan Hajnoczi, 2019/01/23
Re: [Qemu-arm] [PATCH v2 0/5] arm: microbit Non-Volatile Memory Controller, Peter Maydell, 2019/01/24