From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: "Chris Wright" <chrisw@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"wolfgang mueller" <wolfgang@acm.org>,
rot <Frederic.Petrot@imag.fr>,
"QEMU-devel Developers" <qemu-devel@nongnu.org>,
"Andreas Färber" <andreas.faerber@web.de>,
=?ISO-8859-1?Q?Fr=E9d=E9ric_P=E9t?=@gnu.org
Subject: Re: [Qemu-devel] CFP: 1st International QEMU Users Forum
Date: Mon, 29 Nov 2010 10:53:15 +0100 [thread overview]
Message-ID: <4CF3780B.1070904@redhat.com> (raw)
In-Reply-To: <C23F68D6-AF82-4A1E-9D2D-E5899A9A9C2A@suse.de>
On 11/26/10 16:19, Alexander Graf wrote:
>
> On 26.11.2010, at 16:10, Peter Maydell wrote:
>
>> On 26 November 2010 14:21, Anthony Liguori <anthony@codemonkey.ws> wrote:
>>
>>> But the key point is breadth, it should not be a "KVM Forum" but rather an
>>> Open Virtualization conference with topics as high level as cloud software
>>> automation and as low level as asynchronous page faults :-)
>>
>> Does that breadth include the emulation/TCG side of qemu or only
>> the virtualisation/KVM side? I'm never quite sure with titles that
>> just say "Virtualization"...
>
> Historically, virtualization gatherings have been fairly non-tcg friendly. I don't see why we'd have to continue that trend though. A lot of the code actually affects both sides.
IMHO it would be good to have focus on broader QEMU collaboration,
including TCG.
Cheers,
Jes
next prev parent reply other threads:[~2010-11-29 9:53 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 13:42 [Qemu-devel] CFP: 1st International QEMU Users Forum Wolfgang Mueller
2010-11-23 11:25 ` Alexander Graf
2010-11-25 10:30 ` wolfgang mueller
2010-11-25 11:03 ` Alexander Graf
2010-11-25 14:54 ` wolfgang mueller
2010-11-25 23:42 ` Alexander Graf
2010-11-26 13:54 ` Alexander Graf
2010-11-26 14:33 ` Peter Maydell
2010-11-26 15:18 ` Alexander Graf
2010-11-26 16:34 ` wolfgang mueller
2010-11-27 19:00 ` Peter Maydell
2010-11-27 22:26 ` Alexander Graf
2010-11-28 0:09 ` Nathan Froyd
2010-11-28 8:20 ` Frédéric Pétrot
2010-11-28 11:00 ` Alexander Graf
2010-11-29 0:06 ` Nathan Froyd
2010-11-29 6:43 ` Frédéric Pétrot
2010-11-29 13:58 ` Alexander Graf
2010-11-29 14:08 ` Peter Maydell
2010-11-29 15:27 ` Nathan Froyd
2010-11-28 10:55 ` Alexander Graf
2010-11-25 22:53 ` Andreas Färber
2010-11-25 23:17 ` Alexander Graf
2010-11-25 23:48 ` Alexander Graf
2010-11-26 7:56 ` Jes Sorensen
2010-11-26 11:53 ` Alexander Graf
2010-11-26 12:29 ` Jes Sorensen
2010-11-26 13:39 ` Alexander Graf
2010-11-26 14:13 ` Anthony Liguori
2010-11-26 14:15 ` Jes Sorensen
2010-11-26 14:21 ` Anthony Liguori
2010-11-26 15:10 ` Peter Maydell
2010-11-26 15:19 ` Alexander Graf
2010-11-29 9:53 ` Jes Sorensen [this message]
2010-11-26 15:15 ` Alexander Graf
2010-11-26 16:03 ` Anthony Liguori
2010-11-29 7:44 ` Jes Sorensen
2010-12-01 17:57 ` Jes Sorensen
2010-11-29 10:13 ` Stefano Stabellini
2010-11-29 11:30 ` [Qemu-devel] " Paolo Bonzini
[not found] <20101125233507.0D49927D48@zimbra14-e2.priv.proxad.net>
2010-11-26 0:05 ` [Qemu-devel] " François Revol
[not found] <20101125235615.157DC28C0F@zimbra14-e2.priv.proxad.net>
2010-11-26 0:26 ` François Revol
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=4CF3780B.1070904@redhat.com \
--to=jes.sorensen@redhat.com \
--cc==?ISO-8859-1?Q?Fr=E9d=E9ric_P=E9t?=@gnu.org \
--cc=Frederic.Petrot@imag.fr \
--cc=agraf@suse.de \
--cc=andreas.faerber@web.de \
--cc=chrisw@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=wolfgang@acm.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.