[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v3 01/33] Create Resettable QOM interface
From: |
Cornelia Huck |
Subject: |
Re: [Qemu-devel] [PATCH v3 01/33] Create Resettable QOM interface |
Date: |
Tue, 30 Jul 2019 17:47:25 +0200 |
On Tue, 30 Jul 2019 16:08:59 +0200
Damien Hedde <address@hidden> wrote:
> On 7/30/19 3:59 PM, Peter Maydell wrote:
> > On Tue, 30 Jul 2019 at 14:56, Cornelia Huck <address@hidden> wrote:
> >>
> >> On Tue, 30 Jul 2019 14:44:21 +0100
> >> Peter Maydell <address@hidden> wrote:
> >>
> >>> On Tue, 30 Jul 2019 at 14:42, Cornelia Huck <address@hidden> wrote:
> >>>> I'm having a hard time figuring out what a 'cold' or a 'warm' reset is
> >>>> supposed to be... can you add a definition/guideline somewhere?
> >>>
> >>> Generally "cold" reset is "power on" and "warm" is "we were already
> >>> powered-on, but somebody flipped a reset line somewhere".
> >>
> >> Ok, that makes sense... my main concern is to distinguish that in a
> >> generic way, as it is a generic interface. What about adding something
> >> like:
> >>
> >> "A 'cold' reset means that the object to be reset is initially reset; a
> >> 'warm'
> >> reset means that the object to be reset has already been initialized."
> >>
> >> Or is that again too generic?
> >
> > I think it doesn't quite capture the idea -- an object can have already
> > been reset and then get a 'cold' reset: this is like having a powered-on
> > machine and then power-cycling it.
> >
> > The 'warm' reset is the vaguer one, because the specific behaviour
> > is somewhat device-dependent (many devices might not have any
> > difference from 'cold' reset, for those that do the exact detail
> > of what doesn't get reset on warm-reset will vary). But every
> > device should have some kind of "as if you power-cycled it" (or
> > for QEMU, "go back to the same state as if you just started QEMU on the
> > command line"). Our current "reset" method is really cold-reset.
Ah ok, that makes sense.
> >
>
> Exactly. In the following patches, I've tried to replace existing reset
> calls by cold or warm reset depending on whether:
> + it is called through the main system reset -> cold
> + it is called during normal life-time -> warm
>
> But I definitely can add some docs/comments to better explain that.
Yes, that would be great; I think I now understand enough for looking
at the patches.
- Re: [Qemu-devel] [PATCH v3 05/33] Switch to new api in qdev/bus, (continued)
- [Qemu-devel] [PATCH v3 06/33] add the vmstate description for device reset state, Damien Hedde, 2019/07/29
- [Qemu-devel] [PATCH v3 01/33] Create Resettable QOM interface, Damien Hedde, 2019/07/29
- Re: [Qemu-devel] [PATCH v3 01/33] Create Resettable QOM interface, Cornelia Huck, 2019/07/30
- Re: [Qemu-devel] [PATCH v3 01/33] Create Resettable QOM interface, Peter Maydell, 2019/07/30
- Re: [Qemu-devel] [PATCH v3 01/33] Create Resettable QOM interface, Cornelia Huck, 2019/07/30
- Re: [Qemu-devel] [PATCH v3 01/33] Create Resettable QOM interface, Peter Maydell, 2019/07/30
- Re: [Qemu-devel] [PATCH v3 01/33] Create Resettable QOM interface, Damien Hedde, 2019/07/30
- Re: [Qemu-devel] [PATCH v3 01/33] Create Resettable QOM interface,
Cornelia Huck <=
- Re: [Qemu-devel] [PATCH v3 01/33] Create Resettable QOM interface, David Gibson, 2019/07/31
- Re: [Qemu-devel] [PATCH v3 01/33] Create Resettable QOM interface, Christophe de Dinechin, 2019/07/31
[Qemu-devel] [PATCH v3 04/33] make Device and Bus Resettable, Damien Hedde, 2019/07/29
[Qemu-devel] [PATCH v3 07/33] automatically add vmstate for reset support in devices, Damien Hedde, 2019/07/29
[Qemu-devel] [PATCH v3 11/33] hw/s390x/ipl.c: remove qbus_reset_all registration, Damien Hedde, 2019/07/29
[Qemu-devel] [PATCH v3 09/33] add doc about Resettable interface, Damien Hedde, 2019/07/29