From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>,
qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: KVM call minutes for 2012-10-16
Date: Tue, 16 Oct 2012 16:50:47 +0200 [thread overview]
Message-ID: <878vb6mpx4.fsf@elfo.mitica> (raw)
2012-10-16
----------
- cpu as dev
making qdev available to all parts of qemu is the best solution (aliguory)
how does linux-user people think about it?
Eduardo will follow
Objections:
* conceptually it makes no sense to have devices on *-user
* desire of linux-user to maintain the code relativelly small
* really they want less dependencies
Who is going to merge it?
either anthony or andreas through cpu tree
- boot and -bootindex (agraf)
should this overwrote CMOS on PC (anthony)
Always writing nvram makes other things work.
-boot c : means boot with legacy device
with uefi there is a boot variable
-boot c don't make sense out of x86
* make the list of bootable devices visible to the user
and store in nvram?
At this point I got lost, and Anthony/Alex needs to fill the details
of the proposals.
- Command line compatibility patches (marcelo)
merge then directly or through qdev
WARNING: multiple messages have this Message-ID (diff)
From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>,
qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: [Qemu-devel] KVM call minutes for 2012-10-16
Date: Tue, 16 Oct 2012 16:50:47 +0200 [thread overview]
Message-ID: <878vb6mpx4.fsf@elfo.mitica> (raw)
2012-10-16
----------
- cpu as dev
making qdev available to all parts of qemu is the best solution (aliguory)
how does linux-user people think about it?
Eduardo will follow
Objections:
* conceptually it makes no sense to have devices on *-user
* desire of linux-user to maintain the code relativelly small
* really they want less dependencies
Who is going to merge it?
either anthony or andreas through cpu tree
- boot and -bootindex (agraf)
should this overwrote CMOS on PC (anthony)
Always writing nvram makes other things work.
-boot c : means boot with legacy device
with uefi there is a boot variable
-boot c don't make sense out of x86
* make the list of bootable devices visible to the user
and store in nvram?
At this point I got lost, and Anthony/Alex needs to fill the details
of the proposals.
- Command line compatibility patches (marcelo)
merge then directly or through qdev
next reply other threads:[~2012-10-16 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 14:50 Juan Quintela [this message]
2012-10-16 14:50 ` [Qemu-devel] KVM call minutes for 2012-10-16 Juan Quintela
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=878vb6mpx4.fsf@elfo.mitica \
--to=quintela@redhat.com \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.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.