qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: ehrhardt@linux.vnet.ibm.com
Cc: qemu-devel@nongnu.org, avi@qumranet.com, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH] qemu: report issues causing the kvm probe to fail v3
Date: Thu, 08 Jan 2009 14:34:38 -0600	[thread overview]
Message-ID: <4966635E.8090205@us.ibm.com> (raw)
In-Reply-To: <1231422848-32179-1-git-send-email-ehrhardt@linux.vnet.ibm.com>

ehrhardt@linux.vnet.ibm.com wrote:
> From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
>
> The patch applies to upstream qemu as well as kvm-userspace, but since it is
> the qemu configure script I think it should go to upstream qemu (Anthony)
> first and with the next merge to kvm-userspace. On the other hand it is the kvm
> probe so an ack from Avi in case v3 is ok would be reasonable.
>
> *updates*
> v2 - it also reports other errors than just #error preprocessor statements
>      (requested by Avi)
> v3 - In case awk or grep is not installed it now gracfully (silently)
>      fails still disabling kvm (requested by Anthony)
>
> This patch is about reporting more details of the issue if configuring kvm
> fails. Therefore this patch keeps the qemu style configure output which is a
> list of "$Feature $Status", but extend the "no" result like "KVM Support no"
> with some more information.
>
> There might be a lot of things going wrong with that probe and I don't want
> to handle all of them, but if it is one of the known checks e.g. for
> KVM_API_VERSION then we could grep/awk that out and report it. The patch
> reports in case of a known case in the style
> "KVM support no - (Missing KVM capability KVM_CAP_DESTROY_MEMORY_REGION_WORKS)"
>
> In case more than one #error is triggered it creates a comma separated list in
> those brackets and in case it is something else than an #error it just reports
> plain old "no".
>
> Signed-off-by: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
> ---
>
>  configure |   27 ++++++++++++++++++++-------
>  1 file changed, 20 insertions(+), 7 deletions(-)
>
> diff --git a/qemu/configure b/qemu/configure
> --- a/qemu/configure
> +++ b/qemu/configure
>   

Please send against upstream QEMU.

Regards,

Anthony Liguori

  parent reply	other threads:[~2009-01-08 20:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 13:54 [Qemu-devel] [PATCH] qemu: report issues causing the kvm probe to fail v3 ehrhardt
2009-01-08 15:28 ` [Qemu-devel] " Avi Kivity
2009-01-08 20:34 ` Anthony Liguori [this message]
2009-01-09  7:33   ` Christian Ehrhardt
2009-01-15 21:57     ` 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=4966635E.8090205@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=avi@qumranet.com \
    --cc=ehrhardt@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --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).