From: Paolo Bonzini <pbonzini@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH 3/4] Introduce machine state
Date: Tue, 29 Mar 2011 10:14:26 +0200 [thread overview]
Message-ID: <4D9194E2.80405@redhat.com> (raw)
In-Reply-To: <AANLkTim48ir6-PYdLCGBA68mS9_3M+Vi4Syv60EhqSU=@mail.gmail.com>
On 03/28/2011 07:21 PM, Blue Swirl wrote:
>> >
>> > What's the distinction between vm state and machine state?
>
> VM state should be invisible (except for PV devices).
Got it. That's why I called it "emulator state" (a bit generic, but
more precise than vm state: vm_clock for example is guest-visible).
> About 'machine', I was thinking about -M switch to specify
> the emulated machine type.
Yes, makes sense. I actually like the name machine state, as long as
you rename what you called "virtual machine state".
Paolo
next prev parent reply other threads:[~2011-03-29 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 22:28 [Qemu-devel] [PATCH 3/4] Introduce machine state Blue Swirl
2011-03-28 7:25 ` [Qemu-devel] " Paolo Bonzini
2011-03-28 17:21 ` Blue Swirl
2011-03-29 8:14 ` Paolo Bonzini [this message]
2011-03-29 17:50 ` Blue Swirl
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=4D9194E2.80405@redhat.com \
--to=pbonzini@redhat.com \
--cc=blauwirbel@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).