From: Christopher Covington <cov@codeaurora.org>
To: Paolo Bonzini <pbonzini@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Announcing qboot, a minimal x86 firmware for QEMU
Date: Tue, 26 May 2015 17:25:29 -0400 [thread overview]
Message-ID: <5564E4C9.8010906@codeaurora.org> (raw)
In-Reply-To: <55631B3A.7080803@redhat.com>
On 05/25/2015 08:53 AM, Paolo Bonzini wrote:
>
> On 22/05/2015 13:12, Daniel P. Berrange wrote:
>> In
>> particular I don't see why we need to have a SATA controller and ISA/LPC
>> bridge in every virt machine - root PCI bus only should be possible, as you
>> can provide disks via virtio-blk or virtio-scsi and serial, parallel, mouse,
>> floppy via PCI devices and/or by adding a USB bus in the cases where you
>> really need one.
>
> I think removing the ISA/LPC bridge is hard. It includes the real-time
> clock and fw_cfg, for example.
Could VirtIO specified replacements make sense for these peripherals?
Chris
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-05-26 21:25 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 13:51 Announcing qboot, a minimal x86 firmware for QEMU Paolo Bonzini
2015-05-21 13:51 ` [Qemu-devel] " Paolo Bonzini
2015-05-21 15:48 ` Avi Kivity
2015-05-21 16:21 ` Paolo Bonzini
2015-05-21 18:28 ` Avi Kivity
2015-05-21 17:04 ` Jan Kiszka
2015-05-21 17:04 ` [Qemu-devel] " Jan Kiszka
2015-05-22 2:53 ` Yong Wang
2015-05-22 2:53 ` [Qemu-devel] " Yong Wang
2015-05-26 8:47 ` Stefan Hajnoczi
2015-05-26 8:47 ` [Qemu-devel] " Stefan Hajnoczi
2015-06-05 10:42 ` Stefan Hajnoczi
2015-06-05 10:42 ` [Qemu-devel] " Stefan Hajnoczi
2015-05-22 11:01 ` Daniel P. Berrange
2015-05-22 11:04 ` Peter Maydell
2015-05-22 11:12 ` Daniel P. Berrange
2015-05-22 11:21 ` Peter Maydell
2015-05-22 11:33 ` Daniel P. Berrange
2015-05-22 11:34 ` Gerd Hoffmann
2015-05-22 11:34 ` Gerd Hoffmann
2015-05-22 11:42 ` Markus Armbruster
2015-05-22 11:42 ` Markus Armbruster
2015-05-25 12:53 ` Paolo Bonzini
2015-05-26 21:25 ` Christopher Covington [this message]
2015-05-27 9:30 ` Paolo Bonzini
2015-05-27 9:36 ` Avi Kivity
2015-05-27 9:36 ` [Qemu-devel] " Avi Kivity
2015-05-27 11:00 ` Paolo Bonzini
2015-05-27 11:00 ` [Qemu-devel] " Paolo Bonzini
2015-05-27 11:54 ` Peter Maydell
2015-05-27 11:54 ` Peter Maydell
2015-05-27 12:05 ` Paolo Bonzini
2015-05-27 12:05 ` Paolo Bonzini
2015-05-27 12:50 ` Christopher Covington
2015-05-27 12:59 ` Paolo Bonzini
2015-05-27 16:24 ` Dr. David Alan Gilbert
2015-05-27 16:24 ` Dr. David Alan Gilbert
2015-05-22 14:06 ` Gerd Hoffmann
2015-05-22 23:23 ` Kevin O'Connor
2015-05-22 23:23 ` [Qemu-devel] " Kevin O'Connor
2015-05-23 3:55 ` Kevin O'Connor
2015-05-23 3:55 ` [Qemu-devel] " Kevin O'Connor
2015-05-25 6:21 ` Vasiliy Tolstov
2015-05-25 6:21 ` [Qemu-devel] " Vasiliy Tolstov
2015-05-25 15:05 ` Kevin O'Connor
2015-05-25 15:05 ` [Qemu-devel] " Kevin O'Connor
2015-05-25 12:52 ` Paolo Bonzini
2015-05-25 12:52 ` [Qemu-devel] " Paolo Bonzini
2015-05-25 15:11 ` Kevin O'Connor
2015-05-25 15:11 ` [Qemu-devel] " Kevin O'Connor
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=5564E4C9.8010906@codeaurora.org \
--to=cov@codeaurora.org \
--cc=berrange@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.