From: Anthony Liguori <aliguori@us.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [Qemu-commits] [COMMIT 883ecbf] Remove noisy printf when KVMmasks CPU features
Date: Sat, 09 May 2009 08:27:12 -0500 [thread overview]
Message-ID: <4A0584B0.8060201@us.ibm.com> (raw)
In-Reply-To: <4A0544C0.8060201@redhat.com>
Avi Kivity wrote:
> Anthony Liguori wrote:
>> From: Anthony Liguori <aliguori@us.ibm.com>
>>
>> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
>>
>> diff --git a/target-i386/helper.c b/target-i386/helper.c
>> index bdf242b..5c03e3a 100644
>> --- a/target-i386/helper.c
>> +++ b/target-i386/helper.c
>> @@ -102,7 +102,6 @@ static void kvm_trim_features(uint32_t *features,
>> uint32_t supported,
>> for (i = 0; i < 32; ++i) {
>> mask = 1U << i;
>> if ((*features & mask) && !(supported & mask)) {
>> - printf("Processor feature %s not supported by kvm\n",
>> names[i]);
>> *features &= ~mask;
>> }
>> }
>>
>
> That was intentional, I didn't want to silently drop features the user
> requested as those may impact live migration or load/save (or
> application performance).
Why not provide a monitor option to view the list of CPUID features that
are enabled?
printing to stdio is a bad idea. We print the names of pty devices to
stdio and tools have to parse that today. I hope they're sufficiently
robust but this isn't something we want to introduce if we don't have to.
> Maybe it's better to only do that if -cpu was specified on the command
> line; and exit() as well. The user can easily pick up the missing
> bits and remove them from the requested cpu features.
Yes, that's also a good idea.
Regards,
Anthony Liguori
--
Regards,
Anthony Liguori
prev parent reply other threads:[~2009-05-09 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200905082053.n48Kr0rf008206@d03av04.boulder.ibm.com>
2009-05-09 8:54 ` [Qemu-devel] Re: [Qemu-commits] [COMMIT 883ecbf] Remove noisy printf when KVM masks CPU features Avi Kivity
2009-05-09 13:27 ` Anthony Liguori [this message]
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=4A0584B0.8060201@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=avi@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 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).