qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [Qemu-commits] [COMMIT 883ecbf] Remove noisy printf when KVM masks	CPU features
Date: Sat, 09 May 2009 11:54:24 +0300	[thread overview]
Message-ID: <4A0544C0.8060201@redhat.com> (raw)
In-Reply-To: <200905082053.n48Kr0rf008206@d03av04.boulder.ibm.com>

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).

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.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

       reply	other threads:[~2009-05-09  8:54 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 ` Avi Kivity [this message]
2009-05-09 13:27   ` [Qemu-devel] Re: [Qemu-commits] [COMMIT 883ecbf] Remove noisy printf when KVMmasks CPU features Anthony Liguori

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=4A0544C0.8060201@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@us.ibm.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).