[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v6 0/9] Clock framework API
From: |
Dr. David Alan Gilbert |
Subject: |
Re: [PATCH v6 0/9] Clock framework API |
Date: |
Fri, 6 Dec 2019 13:48:59 +0000 |
User-agent: |
Mutt/1.12.1 (2019-06-15) |
* Cleber Rosa (address@hidden) wrote:
> On Thu, Dec 05, 2019 at 12:01:56PM +0100, Philippe Mathieu-Daudé wrote:
> >
> > Understood, thanks for clearing this out!
> >
> > Side note, we don't do cross-arch migration testing, but we talked about
> > having a 'different QEMU version' migration test. When we get a such test
> > setup, it shouldn't be too difficult to evolve to some cross-arch migration
> > test.
> >
>
> +Oksana,
>
> Avocado-VT has had this as a core concept as far as I can remember, and
> it's exposed even as a command line argument:
>
> avocado run --help
> ...
> [--vt-qemu-dst-bin VT_DST_QEMU_BIN]
> ...
>
Yeh, I've run that in the past - it works OK.
Dave
> Oksana is currently working on new migration test cases, and may consider
> looking into adding "different QEMU version" support too.
>
> PS: I have to say, though, that I'm trying to get my mind around
> cross-arch migration being real.
>
> - Cleber.
>
> > > > I hope I'm wrong and confuse, this is a great news for me to know we
> > > > can migrate floats!
> > > >
> > > > > Dave
> > > > >
> > > > > > > So we could store the frequency in clock out and migrate things
> > > > > > > there.
> > > > > > > But since we have no way to ensure all clock out states are
> > > > > > > migrated
> > > > > > > before some device fetch a ClockIn: we'll have to say "don't
> > > > > > > fetch one
> > > > > > > of your ClockIn frequency during migration and migrate the value
> > > > > > > yourself if you need it", pretty much like gpios.
> > > > > > >
> > > > > > > So we will probably migrate all ClockOut and almost all ClockIn.
> > > > > > >
> > > > > > > It would nice if we had a way to ensure clocks are migrated before
> > > > > > > devices try to use them. But I don't think this is possible.
> > > > > > >
> > > > > > > --
> > > > > > > Damien
> > > > > > >
> > > > > >
> > > > > --
> > > > > Dr. David Alan Gilbert / address@hidden / Manchester, UK
> > > > >
> > > >
> > > --
> > > Dr. David Alan Gilbert / address@hidden / Manchester, UK
> > >
> >
--
Dr. David Alan Gilbert / address@hidden / Manchester, UK
- Re: [PATCH v6 0/9] Clock framework API, Peter Maydell, 2019/12/02
- Re: [PATCH v6 0/9] Clock framework API, Damien Hedde, 2019/12/04
- Re: [PATCH v6 0/9] Clock framework API, Philippe Mathieu-Daudé, 2019/12/04
- Re: [PATCH v6 0/9] Clock framework API, Damien Hedde, 2019/12/05
- Re: [PATCH v6 0/9] Clock framework API, Philippe Mathieu-Daudé, 2019/12/05
- Re: [PATCH v6 0/9] Clock framework API, Dr. David Alan Gilbert, 2019/12/05
- Re: [PATCH v6 0/9] Clock framework API, Philippe Mathieu-Daudé, 2019/12/05
- Re: [PATCH v6 0/9] Clock framework API, Dr. David Alan Gilbert, 2019/12/05
- Re: [PATCH v6 0/9] Clock framework API, Philippe Mathieu-Daudé, 2019/12/05
- Re: [PATCH v6 0/9] Clock framework API, Cleber Rosa, 2019/12/06
- Re: [PATCH v6 0/9] Clock framework API,
Dr. David Alan Gilbert <=