qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Xin Tong <xerox.time.tech@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Proper way to walk through all vpcus
Date: Sat, 28 Jan 2012 17:06:54 -0500	[thread overview]
Message-ID: <CALKntY2kAkfSmCHs+mCpVvmDyHk-6+37OitRSWuTOVB3fX6AVA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 311 bytes --]

What is the proper way to iterate over all vcpus in qemu ? below is what i
use in my code. Not sure whether it is the best way, also is a a macro is
qemu to do this ?

      CPUState *curr_cpu = first_cpu;
       for(; curr_cpu != NULL; curr_cpu = curr_cpu->next_cpu) {
               ...
       }

Thanks

Xin

[-- Attachment #2: Type: text/html, Size: 354 bytes --]

             reply	other threads:[~2012-01-28 22:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-28 22:06 Xin Tong [this message]
2012-01-31  8:53 ` [Qemu-devel] Proper way to walk through all vpcus 陳韋任

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=CALKntY2kAkfSmCHs+mCpVvmDyHk-6+37OitRSWuTOVB3fX6AVA@mail.gmail.com \
    --to=xerox.time.tech@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).