From: Anthony Liguori <aliguori@us.ibm.com>
To: Glauber Costa <glommer@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] don't expose lm bit if kernel is not 64-bit capable.
Date: Tue, 03 Feb 2009 15:42:23 -0600 [thread overview]
Message-ID: <4988BA3F.5030605@us.ibm.com> (raw)
In-Reply-To: <5d6222a80902031335l41c90b98y36b0b0f76c6d8987@mail.gmail.com>
Glauber Costa wrote:
> On Tue, Feb 3, 2009 at 7:14 PM, Anthony Liguori <aliguori@us.ibm.com> wrote:
>
>>
>> All I said was that if we used KVM_GET_SUPPORTED_CPUID, we had to do
>> something about save/restore since it can mask arbitrary things.
>>
>>
> Then I misread you.
>
> Who's the subject of your sentence, that can mask arbitrary things?
> kvm.ko in its ioctl,
> or save/restore?
>
Poor wording on my part. Your previous patch called
KVM_GET_SUPPORTED_CPUID which would return the host CPUID bits that KVM
supports. QEMU would then use that set to mask out features for the guest.
But the set of bits KVM returns differs on differing platforms. This
means that you're now enabling features that were not previously
enabled. This isn't a problem, but I'd like to see live migration
handle this gracefully either by saving off the CPUID bits for the guest
and failing appropriately when trying to enable CPUID bits on a platform
that doesn't support it, or an explicit definition of CPUID capabilities.
I don't necessarily have a problem with enabling the most features by
default, I just want migration to fail gracefully.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-02-03 21:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 15:04 [Qemu-devel] [PATCH] don't expose lm bit if kernel is not 64-bit capable Glauber Costa
2009-02-03 15:44 ` Alexander Graf
2009-02-03 15:52 ` Glauber Costa
2009-02-03 17:58 ` Anthony Liguori
2009-02-03 19:35 ` Avi Kivity
2009-02-03 19:37 ` Avi Kivity
2009-02-03 20:00 ` Glauber Costa
2009-02-03 21:14 ` Anthony Liguori
2009-02-03 21:35 ` Glauber Costa
2009-02-03 21:42 ` Anthony Liguori [this message]
2009-02-04 8:10 ` Avi Kivity
2009-02-03 19:37 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2009-02-03 20:15 Glauber Costa
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=4988BA3F.5030605@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=glommer@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).