From: Jan Kiszka <jan.kiszka@siemens.com>
To: Chris Wright <chrisw@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: KVM call agenda for Feb 2
Date: Tue, 02 Feb 2010 11:00:56 +0100 [thread overview]
Message-ID: <4B67F7D8.9050306@siemens.com> (raw)
In-Reply-To: <20100202014232.GJ12142@x200.localdomain>
Chris Wright wrote:
> Please send in any agenda items you are interested in covering.
[not sure, though, if I'll manage to join do to overlapping meeting]
- state of in-kernel APIC/IOAPIC/PIT upstream merge
- road map to get rid of qemu-kvm's slot management
(IMHO: qemu-kvm-0.13)
- any further ongoing/planned upstream merge efforts?
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Chris Wright <chrisw@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: KVM call agenda for Feb 2
Date: Tue, 02 Feb 2010 11:00:56 +0100 [thread overview]
Message-ID: <4B67F7D8.9050306@siemens.com> (raw)
In-Reply-To: <20100202014232.GJ12142@x200.localdomain>
Chris Wright wrote:
> Please send in any agenda items you are interested in covering.
[not sure, though, if I'll manage to join do to overlapping meeting]
- state of in-kernel APIC/IOAPIC/PIT upstream merge
- road map to get rid of qemu-kvm's slot management
(IMHO: qemu-kvm-0.13)
- any further ongoing/planned upstream merge efforts?
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2010-02-02 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 1:42 KVM call agenda for Feb 2 Chris Wright
2010-02-02 1:42 ` [Qemu-devel] " Chris Wright
2010-02-02 10:00 ` Jan Kiszka [this message]
2010-02-02 10:00 ` [Qemu-devel] " Jan Kiszka
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=4B67F7D8.9050306@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=chrisw@redhat.com \
--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.