From: "Andreas Färber" <afaerber@suse.de>
To: quintela@redhat.com
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] VMSTate state of the union
Date: Fri, 18 Jan 2013 13:42:06 +0100 [thread overview]
Message-ID: <50F9431E.3040603@suse.de> (raw)
In-Reply-To: <874niek7u1.fsf@elfo.elfo>
Hi Juan,
Am 18.01.2013 13:13, schrieb Juan Quintela:
> Things missing:
> - cpus: They are blocked by comment that we should be able to sent
> generated fields. Stalled :-(
I'm not sure what you mean here, but I have an old CPU series of yours
on my radar that I am about to partially include in my CPUState part 8
series. A number of questions remained unanswered on your series so I
decided to make a proposal how to proceed.
Cheers,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-01-18 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 12:13 [Qemu-devel] VMSTate state of the union Juan Quintela
2013-01-18 12:42 ` Andreas Färber [this message]
2013-01-18 12:48 ` Peter Maydell
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=50F9431E.3040603@suse.de \
--to=afaerber@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).