All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: qemu-devel@nongnu.org, eswierk@skyportsystems.com,
	pbonzini@redhat.com, peterx@redhat.com, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 5/6] e1000: Choose which set of props to migrate
Date: Thu, 29 Mar 2018 09:08:46 +0100	[thread overview]
Message-ID: <20180329080846.GA2982@work-vm> (raw)
In-Reply-To: <780d6d45-84a6-34db-e65f-3d38a6d0ea66@redhat.com>

* Jason Wang (jasowang@redhat.com) wrote:
> 
> 
> On 2018年03月29日 00:36, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> > 
> > When we're using the subsection we migrate both
> > the 'props' and 'tso_props' data; when we're not using
> > the subsection (to migrate to 2.11 or old machine types) we've
> > got to choose what to migrate in the main structure.
> > 
> > If we're using the subsection migrate 'props' in the main structure.
> > If we're not using the subsection then migrate the last one
> > that changed, which gives behaviour similar to the old behaviour.
> > 
> > 
> 
> But only after migration. Why not simply switch back to the old behavior if
> migrate_tso_props if false?

Because:
  1) We know it's a broken behaviour so it's better not to unfix it
  2) The fix doesn't change guest visible behaviour other than actually
     sending the right packets; so there's no reason to make the fix
     itself dependent on the machine type.
  3) Gating the fix itself on the flag is actually more complex and
     would need checking the flag in lots of places that are already
     pretty complex, rather than what this does which is just check it
     in one place at migration.

Dave
> Thanks
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2018-03-29  8:08 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 [this message]
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 ` [Qemu-devel] [PATCH v2 0/6] e1000 migration changes for 2.12 Jason Wang

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=20180329080846.GA2982@work-vm \
    --to=dgilbert@redhat.com \
    --cc=eswierk@skyportsystems.com \
    --cc=jasowang@redhat.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.