From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] ide: Register vm change state handler once only
Date: Thu, 16 Dec 2010 13:29:04 +0100 [thread overview]
Message-ID: <4D0A0610.6040307@redhat.com> (raw)
In-Reply-To: <1291992477-6388-1-git-send-email-stefanha@linux.vnet.ibm.com>
Am 10.12.2010 15:47, schrieb Stefan Hajnoczi:
> We register the vm change state handler in a PCI BAR map() function.
> This function can be called multiple times throughout the lifetime of a
> PCI IDE device. This results in duplicate vm change state handlers
> being register, none of which are ever unregistered.
>
> Instead, register the vm change state handler in the device's init
> function once and for all.
>
> piix tested, cmd646 and via not tested.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
This conflicts with the AHCI patches. Can you rebase on top of the block
branch?
Kevin
next prev parent reply other threads:[~2010-12-16 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 14:47 [Qemu-devel] [PATCH] ide: Register vm change state handler once only Stefan Hajnoczi
2010-12-16 12:29 ` Kevin Wolf [this message]
2010-12-16 13:28 ` [Qemu-devel] " Stefan Hajnoczi
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=4D0A0610.6040307@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).