From: Jan Kiszka <jan.kiszka@web.de>
To: Juan Quintela <quintela@redhat.com>,
andrzej zaborowski <balrogg@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] vmstate: Useless post_save?
Date: Sat, 08 May 2010 00:39:07 +0200 [thread overview]
Message-ID: <4BE4968B.6050805@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 614 bytes --]
Hi all,
I wondered why we have the post_save callback in vmstate. Conceptually,
it made no sense to me. So I grep'ed for its users - and found exactly
one: tmp105. As suspected, only "strange" code was found:
static void tmp105_post_save(void *opaque)
{
TMP105State *s = opaque;
s->faults = tmp105_faultq[(s->config >> 3) & 3]; /* F */
}
First, s->config cannot be changed by saving the state. And, second,
s->faults is only written by this driver, never read.
Anyone any concerns dropping 'faults' from tmp105 and then dropping the
post_save handler from vmstate?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next reply other threads:[~2010-05-07 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 22:39 Jan Kiszka [this message]
2010-05-09 7:50 ` [Qemu-devel] Re: vmstate: Useless post_save? Juan Quintela
2010-05-11 2:39 ` andrzej zaborowski
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=4BE4968B.6050805@web.de \
--to=jan.kiszka@web.de \
--cc=balrogg@gmail.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 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).