From: Will Deacon <will.deacon@arm.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: "penberg@kernel.org" <penberg@kernel.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH v2 5/5] kvmtool: remove warning about bzImage on non-x86 architectures
Date: Wed, 17 Dec 2014 11:43:36 +0000 [thread overview]
Message-ID: <20141217114335.GE3461@arm.com> (raw)
In-Reply-To: <1418814887-3523-6-git-send-email-andre.przywara@arm.com>
On Wed, Dec 17, 2014 at 11:14:47AM +0000, Andre Przywara wrote:
> Among the architectures supported by kvmtool, only x86 defines a
> bzImage format. So we shouldn't bother users of other architectures
> with a message about something that cannot work.
> Make the bzImage check dependent on compiling for x86.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> ---
> tools/kvm/kvm.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/tools/kvm/kvm.c b/tools/kvm/kvm.c
> index e1b9f6c..21817c3 100644
> --- a/tools/kvm/kvm.c
> +++ b/tools/kvm/kvm.c
> @@ -380,12 +380,15 @@ bool kvm__load_kernel(struct kvm *kvm, const char *kernel_filename,
> die("%s is not an initrd", initrd_filename);
> }
>
> +#ifdef CONFIG_X86
> ret = load_bzimage(kvm, fd_kernel, fd_initrd, kernel_cmdline);
>
> if (ret)
> goto found_kernel;
>
> - pr_warning("%s is not a bzImage. Trying to load it as a flat binary...", kernel_filename);
> + pr_warning("%s is not a bzImage. Trying to load it as an ELF or flat binary...",
> + kernel_filename);
> +#endif
I don't think you need to change the string (at least, that seems to be an
unrelated change).
Will
prev parent reply other threads:[~2014-12-17 11:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 11:14 [PATCH v2 0/5] kvmtool: ARM: fixing initrd, serial IRQs and bzImage message Andre Przywara
2014-12-17 11:14 ` [PATCH v2 1/5] kvmtool: ARM: fix initrd functionality Andre Przywara
2014-12-17 11:14 ` [PATCH v2 2/5] kvmtool: replace GIC specific IRQ type #defines Andre Przywara
2014-12-17 11:42 ` Will Deacon
2014-12-17 11:14 ` [PATCH v2 3/5] kvmtool: ARM: allow level interrupts in device tree Andre Przywara
2014-12-17 11:14 ` [PATCH v2 4/5] kvmtool: ARM: advertise 8250 IRQs as level-triggered Andre Przywara
2014-12-17 11:14 ` [PATCH v2 5/5] kvmtool: remove warning about bzImage on non-x86 architectures Andre Przywara
2014-12-17 11:43 ` Will Deacon [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=20141217114335.GE3461@arm.com \
--to=will.deacon@arm.com \
--cc=andre.przywara@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=penberg@kernel.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