From: Juan Quintela <quintela@redhat.com>
To: Peter Crosthwaite <peter.crosthwaite@petalogix.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
aliguori@us.ibm.com, qemu-devel@nongnu.org,
paul@codesourcery.com
Subject: Re: [Qemu-devel] [PATCH] i2c: factor out VMSD to parent class
Date: Mon, 20 Aug 2012 12:20:03 +0200 [thread overview]
Message-ID: <877gstg90s.fsf@elfo.mitica> (raw)
In-Reply-To: <CAEgOgz7+qatdLNMab6CD_f+5xN6sahNYLT0rwTOmEMcVWFXn-g@mail.gmail.com> (Peter Crosthwaite's message of "Mon, 20 Aug 2012 12:28:10 +1000")
Peter Crosthwaite <peter.crosthwaite@petalogix.com> wrote:
> On Tue, Aug 14, 2012 at 6:46 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
>> On 14 August 2012 09:27, Juan Quintela <quintela@redhat.com> wrote:
>>> "Peter A. G. Crosthwaite" <peter.crosthwaite@petalogix.com> wrote:
>>>> Hi All. PMM raised a query on a recent series of mine (the SSI series) about
>>>> handling VMSD for devices which define state at multiple levels of the QOM
>>>> heirachy.
>>
>>> - If you ask me, I would very much preffer something like PCI devices,
>>> where the 1st field of any specific device is the i2c part. This
>>> would achieve two things:
>>> * all i2c devices would have the common fields at the beggining
>>> * we sent the data for one device in one go, so we will never had
>>> trouble making sure that both devices arrive at the same time, in
>>> the right order, etc.
>>>
>>> - I guess there is same reasy why you want to split the device state,
>>> it could be on the other series where I haven't read it though.
>
> So this is exactly what I have done in the SSI. Correct me if I am
> wrong but it is the same setup as PCI where the VMSTATE_PCI_DEVICE
> (VMSTATE_SSI_SLAVE in my case) is the first field. All I need to do is
> bump version numbers?
I think so. What boards normally use SSI?
Later, Juan.
next prev parent reply other threads:[~2012-08-20 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 8:09 [Qemu-devel] [PATCH] i2c: factor out VMSD to parent class Peter A. G. Crosthwaite
2012-08-14 8:27 ` Juan Quintela
2012-08-14 8:46 ` Peter Maydell
2012-08-20 2:28 ` Peter Crosthwaite
2012-08-20 10:20 ` Juan Quintela [this message]
2012-08-21 4:02 ` Peter Crosthwaite
2012-08-23 11:59 ` Juan Quintela
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=877gstg90s.fsf@elfo.mitica \
--to=quintela@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=paul@codesourcery.com \
--cc=peter.crosthwaite@petalogix.com \
--cc=peter.maydell@linaro.org \
--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).