From: Juan Quintela <quintela@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, mst@redhat.com
Subject: Re: [PATCH v2] device-assignment: Properly terminate vmsd.fields
Date: Wed, 19 Jan 2011 16:40:55 +0100 [thread overview]
Message-ID: <m3d3nsvr3s.fsf@trasno.org> (raw)
In-Reply-To: <20110117171218.29227.19416.stgit@s20.home> (Alex Williamson's message of "Mon, 17 Jan 2011 10:17:49 -0700")
Alex Williamson <alex.williamson@redhat.com> wrote:
> The vmsd code expects the fields structure to be properly terminated,
> not NULL. An assigned device should never be saved or restored, and
> recent qemu fixes to the no_migrate flag should ensure this, but let's
> avoid setting the wrong precedent.
>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Acked-by: Juan Quintela <quintela@redhat.com>
next prev parent reply other threads:[~2011-01-19 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 17:17 [PATCH v2] device-assignment: Properly terminate vmsd.fields Alex Williamson
2011-01-19 15:40 ` Juan Quintela [this message]
2011-01-20 16:08 ` Marcelo Tosatti
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=m3d3nsvr3s.fsf@trasno.org \
--to=quintela@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox