From: Juan Quintela <quintela@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: alevy@redhat.com, yhalperi@redhat.com, qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/2] hda: do not mix output and input stream states, RHBZ #740493
Date: Tue, 04 Oct 2011 19:21:33 +0200 [thread overview]
Message-ID: <m3obxwbrky.fsf@trasno.mitica> (raw)
In-Reply-To: <1317744432-1874-3-git-send-email-marcandre.lureau@redhat.com> ("Marc-André Lureau"'s message of "Tue, 4 Oct 2011 18:07:12 +0200")
"Marc-André Lureau" <marcandre.lureau@gmail.com> wrote:
> Windows 7 may use the same stream number for input and output.
> Current code will confuse streams.
>
> NB: I wonder if this patch breaks migration code because of
> this change:
> - VMSTATE_BOOL_ARRAY(running, HDAAudioState, 16),
> + VMSTATE_BOOL_ARRAY(running, HDAAudioState, 2 * 16),
It does :-(
Two questions to know how to handle this.
a) My understanding of this patch is that we move from an array of 16
bools representing anything to one array where the 1st 16 represent if
there are input and the 2nd 16's reprosenting if there are output for
that channel.
So, what we should do if we migrate from one old version that only has
16 bools? My understanding is that copying directly is not gonna work?
b) Just in case it makes "compatibility" easier.
Is the running array normally all false or similar? If so, we could
just sent the other 16th values only if they are different of false.
(if this is true, it is interesting to put in the 1st slots the ones
that are more probable to be true).
Later, Juan.
next prev parent reply other threads:[~2011-10-04 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 16:07 [Qemu-devel] [PATCH 0/2] HDA fixes for Windows 7 Marc-André Lureau
2011-10-04 16:07 ` [Qemu-devel] [PATCH 1/2] hda: do not mix output and input streams, RHBZ #740493 Marc-André Lureau
2011-10-04 16:07 ` [Qemu-devel] [PATCH 2/2] hda: do not mix output and input stream states, " Marc-André Lureau
2011-10-04 17:21 ` Juan Quintela [this message]
2011-10-05 1:43 ` Marc-André Lureau
2011-10-14 11:38 ` Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2011-10-17 10:58 [Qemu-devel] [PATCH 1/2] hda: do not mix output and input streams, " Marc-André Lureau
2011-10-17 10:58 ` [Qemu-devel] [PATCH 2/2] hda: do not mix output and input stream states, " Marc-André Lureau
2011-10-25 14:53 [Qemu-devel] [PATCH 1/2] hda: do not mix output and input streams, " Marc-André Lureau
2011-10-25 14:53 ` [Qemu-devel] [PATCH 2/2] hda: do not mix output and input stream states, " Marc-André Lureau
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=m3obxwbrky.fsf@trasno.mitica \
--to=quintela@redhat.com \
--cc=alevy@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yhalperi@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;
as well as URLs for NNTP newsgroup(s).