qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chao Peng <chao.p.peng@linux.intel.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel@nongnu.org, rjones@redhat.com,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] Status of q35-lite?
Date: Tue, 13 Jun 2017 14:07:04 +0800	[thread overview]
Message-ID: <1497334024.13717.8.camel@linux.intel.com> (raw)
In-Reply-To: <20170524150753.GB23327@stefanha-x1.localdomain>

On Wed, 2017-05-24 at 16:07 +0100, Stefan Hajnoczi wrote:
> Hi Chao,
> Last year there was an effort to make "built-in" hardware optional so
> that VMs can be launched with a minimal set of devices.  You made
> SATA,
> PIT, and SMBus optional.
> 
> What is the current status of this work?
> 
> Are there more devices that could benefit from an optional switch?

Hi Stefan, in terms of making device optional, we don't have more
follow-ups basically because other build-in devices do not have
significant performance impact. For other optimizations (like
optimizing/skipping BIOS), we are still working on them.

Chao
> 
> For reference, here is the discussion that kicked of the effort to
> make
> some core devices optional:
> "[RFC 0/9] Introduce light weight PC platform pc-lite"
> https://lists.nongnu.org/archive/html/qemu-devel/2016-06/msg04842.html
> 
> Stefan

  parent reply	other threads:[~2017-06-13  6:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24 15:07 [Qemu-devel] Status of q35-lite? Stefan Hajnoczi
2017-05-30 15:06 ` Stefan Hajnoczi
2017-06-13  6:07 ` Chao Peng [this message]
2017-06-13  9:50   ` Stefan Hajnoczi

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=1497334024.13717.8.camel@linux.intel.com \
    --to=chao.p.peng@linux.intel.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    --cc=stefanha@redhat.com \
    /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).