All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>,
	qemu-devel@nongnu.org, eswierk@skyportsystems.com,
	pbonzini@redhat.com
Cc: quintela@redhat.com, peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/6] e1000 migration changes for 2.12
Date: Fri, 30 Mar 2018 10:01:16 +0800	[thread overview]
Message-ID: <0ce442bf-d277-6e1a-d6c0-cbf5fc8664d6@redhat.com> (raw)
In-Reply-To: <20180328163630.48576-1-dgilbert@redhat.com>



On 2018年03月29日 00:36, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>
> Hi,
>    This set of patches change the e1000 migration code to make
> it easier to keep with compatibility with older versions in backwards
> migration.
>
> I think the first 3 patches are fairly uncontrovercial and I would like
> them for 2.12; it would be nice to have the lot since changing them
> after we've shipped is much more difficult.
>
> v2
>    Ed and Paolo answered my question that I asked in the cover letter;
> and I think I've followed the advice - although my testing has been
> very light.  The new patches do two things:
>     a) When we receive a stream without the subsection we duplicate the
> received pops state into both props and tso_props.
>     b) When we send without the subsection we decide which set to send
> in the main part of the state based on which state was last changed.
>
> Dave
>
> Dr. David Alan Gilbert (6):
>    e1000: Convert v3 fields to subsection
>    e1000: Dupe offload data on reading old stream
>    e1000: wire new subsection to property
>    e1000: Migrate props via a temporary structure
>    e1000: Choose which set of props to migrate
>    e1000: Old machine types, turn new subsection off
>
>   hw/net/e1000.c      | 103 ++++++++++++++++++++++++++++++++++++++++------------
>   include/hw/compat.h |   4 ++
>   2 files changed, 84 insertions(+), 23 deletions(-)
>

Reviewed-by: Jason Wang <jasowang@redhat.com>

      parent reply	other threads:[~2018-03-30  2:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-28 16:36 [Qemu-devel] [PATCH v2 0/6] e1000 migration changes for 2.12 Dr. David Alan Gilbert (git)
2018-03-28 16:36 ` [Qemu-devel] [PATCH v2 1/6] e1000: Convert v3 fields to subsection Dr. David Alan Gilbert (git)
2018-03-28 16:36 ` [Qemu-devel] [PATCH v2 2/6] e1000: Dupe offload data on reading old stream Dr. David Alan Gilbert (git)
2018-03-28 16:36 ` [Qemu-devel] [PATCH v2 3/6] e1000: wire new subsection to property Dr. David Alan Gilbert (git)
2018-03-28 16:36 ` [Qemu-devel] [PATCH v2 4/6] e1000: Migrate props via a temporary structure Dr. David Alan Gilbert (git)
2018-03-28 16:36 ` [Qemu-devel] [PATCH v2 5/6] e1000: Choose which set of props to migrate Dr. David Alan Gilbert (git)
2018-03-28 22:47   ` Ed Swierk
2018-03-29  1:55   ` Jason Wang
2018-03-29  8:08     ` Dr. David Alan Gilbert
2018-03-29  8:26       ` Jason Wang
2018-03-29  8:44         ` Dr. David Alan Gilbert
2018-03-30  2:00           ` Jason Wang
2018-04-04 15:58   ` Paolo Bonzini
2018-03-28 16:36 ` [Qemu-devel] [PATCH v2 6/6] e1000: Old machine types, turn new subsection off Dr. David Alan Gilbert (git)
2018-03-30  2:01 ` Jason Wang [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=0ce442bf-d277-6e1a-d6c0-cbf5fc8664d6@redhat.com \
    --to=jasowang@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eswierk@skyportsystems.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.