From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Chao Peng <chao.p.peng@linux.intel.com>,
Haozhong Zhang <haozhong.zhang@intel.com>,
Xiao Guangrong <guangrong.xiao@linux.intel.com>,
Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, anthony.xu@intel.com,
gor Mammedov <imammedo@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [RFC 0/9] Introduce light weight PC platform pc-lite
Date: Mon, 20 Jun 2016 13:31:25 +0100 [thread overview]
Message-ID: <20160620123125.GH14100@stefanha-x1.localdomain> (raw)
In-Reply-To: <76b78e27-c14f-ebb5-baab-a0bf75a60a10@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 342 bytes --]
On Mon, Jun 20, 2016 at 08:54:10AM +0200, Paolo Bonzini wrote:
> I wonder if Linux could run as a multiboot-compliant ELF file, and what
> the performance would be... Multiboot omits the real mode stub.
The Linux boot protocol does not require real mode. I think "64-bit
BOOT PROTOCOL" in Documentation/x86/boot.txt could be used.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-06-20 12:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 8:14 [Qemu-devel] [RFC 0/9] Introduce light weight PC platform pc-lite Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 1/9] acpi: introduce light weight ACPI PM emulation pm-lite Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 2/9] pci: introduce light weight PCIE Host emulation pci-lite Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 3/9] acpi: add support for pc-lite platform Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 4/9] acpi: expose data structurs and functions of BIOS linker loader Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 5/9] acpi: expose acpi_checksum() Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 6/9] acpi: patch guest ACPI for pc-lite Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 7/9] pc: skip setting CMOS data when RTC device is unavailable Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 8/9] pc: support direct loading protected/long mode kernel Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 9/9] pc: introduce light weight PC board pc-lite Chao Peng
2016-06-17 13:24 ` [Qemu-devel] [RFC 0/9] Introduce light weight PC platform pc-lite Paolo Bonzini
2016-06-20 6:01 ` Chao Peng
2016-06-20 6:54 ` Paolo Bonzini
2016-06-20 12:31 ` Stefan Hajnoczi [this message]
2016-06-20 13:00 ` Paolo Bonzini
2016-06-21 1:23 ` Chao Peng
2016-06-21 16:44 ` Michael S. Tsirkin
2016-06-23 8:32 ` Chao Peng
2016-06-23 12:44 ` Paolo Bonzini
2016-06-24 6:39 ` Claudio Fontana
2016-06-24 6:41 ` Claudio Fontana
2016-06-24 6:53 ` Paolo Bonzini
2016-06-27 2:55 ` Claudio Fontana
2016-06-28 9:27 ` Chao Peng
2016-06-20 10:36 ` Dr. David Alan Gilbert
2016-06-19 3:51 ` Michael S. Tsirkin
2016-06-20 6:12 ` Chao Peng
2016-06-23 12:55 ` Daniel P. Berrange
2016-06-28 10:10 ` Chao Peng
2016-06-28 10:26 ` Daniel P. Berrange
2016-06-19 8:21 ` Claudio Fontana
2016-06-20 6:30 ` Chao Peng
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=20160620123125.GH14100@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=anthony.xu@intel.com \
--cc=chao.p.peng@linux.intel.com \
--cc=ehabkost@redhat.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=haozhong.zhang@intel.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).