From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Drop redundant resume_all_vcpus from main
Date: Thu, 02 May 2013 13:20:25 +0200 [thread overview]
Message-ID: <51824BF9.4030205@siemens.com> (raw)
In-Reply-To: <50333245.3060501@redhat.com>
On 2012-08-21 09:01, Paolo Bonzini wrote:
> Il 20/08/2012 20:11, Jan Kiszka ha scritto:
>> VCPUs are either resumed directly via vm_start, after the incoming
>> migration is done, or when a continue command is issued. We don't need
>> the explicit resume before entering main_loop.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>>
>> I was adding nesting support to pause/resume_all_vcpus, and that
>> stumbled over the imbalance below.
>>
>> vl.c | 1 -
>> 1 files changed, 0 insertions(+), 1 deletions(-)
>>
>> diff --git a/vl.c b/vl.c
>> index ebee867..231d3ab 100644
>> --- a/vl.c
>> +++ b/vl.c
>> @@ -3757,7 +3757,6 @@ int main(int argc, char **argv, char **envp)
>>
>> os_setup_post();
>>
>> - resume_all_vcpus();
>> main_loop();
>> bdrv_close_all();
>> pause_all_vcpus();
>>
>
> Makes sense. Do we need a "main loop and similar" tree, or can that
> tree be just uq/master now that qemu-kvm.c is dying?
>
> Paolo
>
Just noticed that this cleanup didn't make it into upstream back then.
Not truly trivial, but also not really risky.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-05-02 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 18:11 [Qemu-devel] [PATCH] Drop redundant resume_all_vcpus from main Jan Kiszka
2012-08-21 7:01 ` Paolo Bonzini
2012-08-21 7:24 ` Jan Kiszka
2013-05-02 11:20 ` Jan Kiszka [this message]
2013-05-02 11:55 ` Andreas Färber
2013-05-02 12:06 ` Jan Kiszka
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=51824BF9.4030205@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=aliguori@us.ibm.com \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.