From: puckbee <puckbee@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] The details of round robin of multi-vcpu in TCG mode
Date: Tue, 16 Apr 2013 09:51:11 +0800 [thread overview]
Message-ID: <516CAE8F.3030905@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]
Hi there:
Sorry to post this problem a second time, for I thought maybe the
question is not descripted clearly.
I'm studying the execution details of multi-vcpu in TCG mode.
The vcpus in TCG mode are executed one by one in a sequencial way,
according to some articles about Qemu.
I read the function [tcg_exec_all] in Qemu 1.3.0 as bellow, but the
implementation is not as expected.
[tcg_exec_all] will finally call [cpu_exec] to excute a loop to excute
the TBs in code cache
So,how does these functions control the running time of each VCPU?
That is,when will the execution of one VCPU return, in order to execute
the next_cpu in the loop of [tcg_exec_all].
Using alarm timer or other methonds?
staticvoidtcg_exec_all(void)
{
intr;
/* Account partial waits to the vm_clock. */
qemu_clock_warp(vm_clock);
if(next_cpu==NULL){
next_cpu=first_cpu;
}
*for(;next_cpu!=NULL&&!exit_request;next_cpu=next_cpu->next_cpu){*
CPUArchState*env=next_cpu;
CPUState*cpu=ENV_GET_CPU(env);
qemu_clock_enable(vm_clock,
(env->singlestep_enabled&SSTEP_NOTIMER)==0);
if(cpu_can_run(cpu)){
***r****=****tcg_cpu_exec**(**env**);*
if(r==EXCP_DEBUG){
cpu_handle_guest_debug(env);
break;
}
}elseif(cpu->stop||cpu->stopped){
break;
}
}
exit_request=0;
}
Yours
Puck
[-- Attachment #2: Type: text/html, Size: 25300 bytes --]
next reply other threads:[~2013-04-16 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 1:51 puckbee [this message]
2013-04-16 2:53 ` [Qemu-devel] The details of round robin of multi-vcpu in TCG mode li guang
2013-04-18 11:54 ` [Qemu-devel] Is Qemu now support x2apic in TCG mode? puckbee
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=516CAE8F.3030905@gmail.com \
--to=puckbee@gmail.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).