From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Igor Mammedov" <imammedo@redhat.com>,
"Don Slutz" <Don@CloudSwitch.Com>,
"Andreas Färber" <afaerber@suse.de>
Subject: [Qemu-devel] [PATCH 0/6] short x86 CPU init cleanup (v3)
Date: Tue, 4 Dec 2012 17:34:37 -0200 [thread overview]
Message-ID: <1354649683-9078-1-git-send-email-ehabkost@redhat.com> (raw)
Changes v3:
- Fix memory leak spotted by Igor, on patch 2
Changes v2:
- Coding style changes (patches 1-2)
- Use "return -1" directly instead of "goto error" on cpu_x86_find_by_name()
(patch 2)
This series is based on the qom-cpu branch from afaerber's tree. The full
branch can be found in a git tree, at:
git://github.com/ehabkost/qemu-hacks.git cpu-init-cleanup-short-v3
https://github.com/ehabkost/qemu-hacks/tree/cpu-init-cleanup-short-v3
References to previous versions:
v2: http://marc.info/?l=qemu-devel&m=135464803607329
v1: http://article.gmane.org/gmane.comp.emulators.qemu/182713
previous (long) cleanup series:
http://article.gmane.org/gmane.comp.emulators.qemu/180137
Eduardo Habkost (2):
target-i386/cpu.c: coding style fixes
target-i386: cpu: separate feature string parsing from CPU model
lookup
Igor Mammedov (4):
target-i386: use define for cpuid vendor string size
target-i386: postpone cpuid_level update to realize time
add visitor for parsing hz[KMG] input string
target-i386: use visit_type_hz to parse tsc_freq property value
qapi/qapi-visit-core.c | 11 +++++
qapi/qapi-visit-core.h | 2 +
qapi/string-input-visitor.c | 22 ++++++++++
target-i386/cpu.c | 105 ++++++++++++++++++++++++++++----------------
target-i386/cpu.h | 2 +
5 files changed, 103 insertions(+), 39 deletions(-)
--
1.7.11.7
next reply other threads:[~2012-12-04 19:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 19:34 Eduardo Habkost [this message]
2012-12-04 19:34 ` [Qemu-devel] [PATCH 1/6] target-i386/cpu.c: coding style fixes Eduardo Habkost
2012-12-04 19:40 ` Igor Mammedov
2012-12-04 19:34 ` [Qemu-devel] [PATCH 2/6] target-i386: cpu: separate feature string parsing from CPU model lookup Eduardo Habkost
2012-12-04 19:47 ` Igor Mammedov
2012-12-05 15:58 ` Andreas Färber
2012-12-04 19:34 ` [Qemu-devel] [PATCH 3/6] target-i386: use define for cpuid vendor string size Eduardo Habkost
2012-12-04 19:38 ` Eduardo Habkost
2012-12-05 11:29 ` Andreas Färber
2012-12-05 11:51 ` Eduardo Habkost
2012-12-05 12:03 ` Igor Mammedov
2012-12-04 19:34 ` [Qemu-devel] [PATCH 4/6] target-i386: postpone cpuid_level update to realize time Eduardo Habkost
2012-12-04 19:36 ` Eduardo Habkost
2012-12-04 19:34 ` [Qemu-devel] [PATCH 5/6] add visitor for parsing hz[KMG] input string Eduardo Habkost
2012-12-04 19:41 ` Eduardo Habkost
2012-12-04 23:43 ` Andreas Färber
2012-12-05 17:52 ` mdroth
2012-12-05 19:21 ` Eduardo Habkost
2012-12-05 21:00 ` mdroth
2012-12-06 20:49 ` Igor Mammedov
2012-12-04 19:34 ` [Qemu-devel] [PATCH 6/6] target-i386: use visit_type_hz to parse tsc_freq property value Eduardo Habkost
2012-12-04 19:55 ` Eduardo Habkost
2012-12-05 16:24 ` [Qemu-devel] [PATCH 0/6] short x86 CPU init cleanup (v3) Andreas Färber
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=1354649683-9078-1-git-send-email-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=Don@CloudSwitch.Com \
--cc=afaerber@suse.de \
--cc=imammedo@redhat.com \
--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 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).