All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>, Anthony Liguori <aliguori@us.ibm.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, kvm <kvm@vger.kernel.org>
Subject: Re: qemu-kvm: Remaining relevant bits in kvm/
Date: Mon, 3 Oct 2011 17:04:05 -0300	[thread overview]
Message-ID: <20111003200405.GD20893@amt.cnet> (raw)
In-Reply-To: <4E885A28.40006@redhat.com>

On Sun, Oct 02, 2011 at 02:33:44PM +0200, Avi Kivity wrote:
> On 09/29/2011 08:10 PM, Marcelo Tosatti wrote:
> >On Wed, Sep 28, 2011 at 05:05:57PM +0200, Jan Kiszka wrote:
> >>  Hi all,
> >>
> >>  in order to reduce the diff between qemu-kvm.git and upstream,
> >>  getting rid of the kvm subdirectory would be nice. What bits there
> >>  are actually still in use today?
> >>
> >>   From the top of my head, I only remember running kvm_stat and
> >>  scripts/vmxcap from time to time. Obviously, there is nothing
> >>  actively built anymore during normal qemu production. So what is the
> >>  role of, e.g.,
> >>
> >>   - kvm/bios
> >
> >Does not exist.
> >
> >>   - kvm/extboot
> >>   - kvm/vgabios
> >
> >Not needed, pc-bios/ version used instead.
> >
> 
> Do we have everything in kvm/vgabios merged?  Lots of vga modelines IIRC.

There is one modeline pending:

http://lists.gnu.org/archive/html/qemu-devel/2010-12/msg00000.html

Anthony, can you please add that patch to qemu's vgabios so we can drop
kvm's entirely?


      reply	other threads:[~2011-10-03 20:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-28 15:05 qemu-kvm: Remaining relevant bits in kvm/ Jan Kiszka
2011-09-29 17:10 ` Marcelo Tosatti
2011-09-29 17:42   ` Jan Kiszka
2011-10-02 12:33   ` Avi Kivity
2011-10-03 20:04     ` Marcelo Tosatti [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=20111003200405.GD20893@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.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 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.