From: Anthony Liguori <anthony@codemonkey.ws>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] QMP: Really move the RESET event to qemu_system_reset()
Date: Wed, 10 Mar 2010 09:24:09 -0600 [thread overview]
Message-ID: <4B97B999.4060404@codemonkey.ws> (raw)
In-Reply-To: <20100310115450.1f5f6c8d@redhat.com>
On 03/10/2010 08:54 AM, Luiz Capitulino wrote:
> Something bad has happened in the merge of commit 0ee44250, as
> the log message says it's supposed to be in qemu_system_reset()
> but it is do_vm_stop().
>
> Possibly, it was a problem with the conflict resolution with
> ea375f9a (which has been merged first).
>
It's not due to conflict resolution, it's due to patch applying with
fuzz. I'm not sure I have a great solution to avoid this.
Regards,
Anthony Liguori
> This commit moves (again) the RESET event into qemu_system_reset().
>
> Signed-off-by: Luiz Capitulino<lcapitulino@redhat.com>
> ---
> vl.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/vl.c b/vl.c
> index d8328c7..fd89e50 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -3148,8 +3148,6 @@ static void do_vm_stop(int reason)
> vm_state_notify(0, reason);
> monitor_protocol_event(QEVENT_STOP, NULL);
> }
> -
> - monitor_protocol_event(QEVENT_RESET, NULL);
> }
>
> void qemu_register_reset(QEMUResetHandler *func, void *opaque)
> @@ -3182,6 +3180,7 @@ void qemu_system_reset(void)
> QTAILQ_FOREACH_SAFE(re,&reset_handlers, entry, nre) {
> re->func(re->opaque);
> }
> + monitor_protocol_event(QEVENT_RESET, NULL);
> cpu_synchronize_all_post_reset();
> }
>
>
next prev parent reply other threads:[~2010-03-10 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 14:54 [Qemu-devel] [PATCH] QMP: Really move the RESET event to qemu_system_reset() Luiz Capitulino
2010-03-10 15:24 ` Anthony Liguori [this message]
2010-03-10 15:27 ` Anthony Liguori
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=4B97B999.4060404@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aliguori@us.ibm.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).