From: Kevin Wolf <kwolf@redhat.com>
To: quintela@redhat.com
Cc: i.mitsyanko@samsung.com, jan.kiszka@siemens.com,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
aderumier@odiso.com, agraf@suse.de, yamahata@valinux.co.jp,
afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v3 2/2] ahci: add migration support
Date: Tue, 15 Jan 2013 16:02:36 +0100 [thread overview]
Message-ID: <50F56F8C.3020507@redhat.com> (raw)
In-Reply-To: <87bocqts1q.fsf@elfo.mitica>
Am 15.01.2013 15:54, schrieb Juan Quintela:
> Jason Baron <jbaron@redhat.com> wrote:
>> From: Jason Baron <jbaron@redhat.com>
>>
>> I've tested these patches by migrating Windows 7 and Fedora 17 guests (while
>> uunder i/o) on both piix with ahci attached and on q35 (which has a built-in
>> ahci controller).
>>
>> Changes from v2:
>> -migrate all relevant ahci fields
>> -flush any pending i/o in 'post_load'
>>
>> Changes from v1:
>> -extend Andreas Färber's patch
>>
>> Signed-off-by: Jason Baron <jbaron@redhat.com>
>> Signed-off-by: Andreas Färber <afaerber@suse.de>
>> Cc: Alexander Graf <agraf@suse.de>
>> Cc: Kevin Wolf <kwolf@redhat.com>
>> Cc: Juan Quintela <quintela@redhat.com>
>> Cc: Igor Mitsyanko <i.mitsyanko@samsung.com>
>> ---
>> hw/ide/ahci.c | 80 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
>> hw/ide/ahci.h | 10 +++++++
>> hw/ide/ich.c | 11 +++++--
>> 3 files changed, 97 insertions(+), 4 deletions(-)
>>
>> diff --git a/hw/ide/ahci.c b/hw/ide/ahci.c
>> index 72cd1c8..96f224b 100644
>> --- a/hw/ide/ahci.c
>> +++ b/hw/ide/ahci.c
>> @@ -1199,6 +1199,81 @@ void ahci_reset(AHCIState *s)
>> }
>> }
>>
>> +static const VMStateDescription vmstate_ahci_device = {
>> + .name = "ahci port",
>
> I will try to be consistent here, vmstate_ahci_port or "ahci device"
Hm, I think calling it port makes much clearer what it really is, but
the struct is called AHCIDevice. Not sure if renaming it is worth it,
but if you all think it is, I can do it.
>> index de39b30..0c4206a 100644
>> --- a/hw/ide/ich.c
>> +++ b/hw/ide/ich.c
>> @@ -79,9 +79,14 @@
>> #define ICH9_IDP_INDEX 0x10
>> #define ICH9_IDP_INDEX_LOG2 0x04
>>
>> -static const VMStateDescription vmstate_ahci = {
>> +static const VMStateDescription vmstate_ich9_ahci = {
>> .name = "ahci",
>> - .unmigratable = 1,
>
>
> I will also preffer here to be consistent between name of the variable
> ad name of the section.
Ok, I'll change this one.
> Both comments are stylist, nothing big. Change if you have to
> resent/whoever merge it.
>
> Kevin?
I'm addressing my own comments right now and will send a v4.
Kevin
prev parent reply other threads:[~2013-01-15 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 19:44 [Qemu-devel] [PATCH v3 0/2] add ahci migration Jason Baron
2013-01-04 19:44 ` [Qemu-devel] [PATCH v3 1/2] ahci: remove unused AHCIDevice fields Jason Baron
2013-01-15 14:51 ` Juan Quintela
2013-01-04 19:44 ` [Qemu-devel] [PATCH v3 2/2] ahci: add migration support Jason Baron
2013-01-10 11:52 ` Kevin Wolf
2013-01-15 14:54 ` Juan Quintela
2013-01-15 15:02 ` Kevin Wolf [this message]
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=50F56F8C.3020507@redhat.com \
--to=kwolf@redhat.com \
--cc=aderumier@odiso.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=i.mitsyanko@samsung.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=yamahata@valinux.co.jp \
/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).