From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] multiboot: Prevent loading of x86_64 images
Date: Thu, 19 Aug 2010 17:12:54 +0300 [thread overview]
Message-ID: <4C6D3BE6.8080706@redhat.com> (raw)
In-Reply-To: <FF740AF5-7120-483B-8442-F4EC7F7DF68F@suse.de>
On 08/19/2010 05:10 PM, Alexander Graf wrote:
>>>
>>>> We rely on the existing behaviour in kvm-unit-tests.git. Tests (.flat files) are 64-bit elf binaries that are loaded in 32-bit more and switch immediately to 64-bit.
>>>>
>>>> We can easily wrap them in a 32-bit elf, but that's a needless complication.
>>> Well, but if they wouldn't work in grub that doesn't help too much, right?
>> Since the processor vendors don't use kvm-unit-tests.git to test their silicon, most people use qemu -kernel to run the unit tests, not grub.
> It would potentially also help the unit tests, as running them in grub would allow for easy verification on real hardware too.
True. We need to write an INT 10 driver and a serial driver for this to
work.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-08-19 14:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 11:24 [Qemu-devel] [PATCH] multiboot: Prevent loading of x86_64 images Adam Lackorzynski
2010-08-19 11:27 ` Alexander Graf
2010-08-19 11:36 ` Adam Lackorzynski
2010-08-19 11:40 ` Alexander Graf
2010-08-19 12:32 ` Adam Lackorzynski
2010-08-19 12:34 ` Alexander Graf
2010-08-19 12:49 ` Adam Lackorzynski
2010-08-19 13:01 ` Alexander Graf
2010-08-20 18:47 ` Rene Rebe
2010-08-19 13:02 ` Avi Kivity
2010-08-19 13:57 ` Alexander Graf
2010-08-19 14:05 ` Avi Kivity
2010-08-19 14:10 ` Alexander Graf
2010-08-19 14:12 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-02 20:28 Adam Lackorzynski
2010-09-25 8:51 Adam Lackorzynski
2010-11-04 22:22 Adam Lackorzynski
2010-11-16 20:09 ` 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=4C6D3BE6.8080706@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--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).