From: "Michael S. Tsirkin" <mst@redhat.com>
To: seabios@seabios.org, qemu-devel <qemu-devel@nongnu.org>
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>,
dwmw2@infradead.org, jljusten@gmail.com,
Kevin O'Connor <kevin@koconnor.net>,
ddutile@redhat.com, Anthony Liguori <anthony@codemonkey.ws>,
lersek@redhat.com
Subject: Re: [Qemu-devel] KVM call agenda for 2013-06-11
Date: Mon, 10 Jun 2013 19:50:41 +0300 [thread overview]
Message-ID: <20130610165041.GA31210@redhat.com> (raw)
In-Reply-To: <20130604132431.GA24301@redhat.com>
On Tue, Jun 04, 2013 at 04:24:31PM +0300, Michael S. Tsirkin wrote:
> Juan is not available now, and Anthony asked for
> agenda to be sent early.
> So here comes:
>
> Agenda for the meeting Tue, June 11:
>
> - Generating acpi tables, redux
I've just posted a proof of concept patch on list,
as promised.
Since Anthony (apparently, alone?) is objecting to
this on principle I don't think there's need to spend
time testing it at this stage:
I'd like to use the meeting to discuss the requirements
coming from ACPI spec and how this patch
addresses them, and how generating the SSDT table
in qemu makes life easier, and would be awkward in
the bios.
Also, to address comments raised on the previous
conf call.
I hope that at the end of the meeting we'll be
able to arrive at concensus opinion
re the usefulness of supplying ACPI tables to
guests (on PC only).
> Please, send any topic that you are interested in covering.
>
> Thanks, MST
>
> --
> MST
next prev parent reply other threads:[~2013-06-10 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 13:24 [Qemu-devel] KVM call agenda for 2013-06-11 Michael S. Tsirkin
2013-06-10 16:50 ` Michael S. Tsirkin [this message]
2013-06-11 15:45 ` Michael S. Tsirkin
2013-06-11 18:06 ` Laszlo Ersek
2013-06-11 19:15 ` Michael S. Tsirkin
2013-06-11 18:38 ` Anthony Liguori
2013-06-11 19:22 ` Michael S. Tsirkin
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=20130610165041.GA31210@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=ddutile@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jljusten@gmail.com \
--cc=kevin@koconnor.net \
--cc=kvm@vger.kernel.org \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=seabios@seabios.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 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).