From: Anthony Liguori <anthony@codemonkey.ws>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: libvir-list@redhat.com, Jiri Denemark <jdenemar@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH qemu v3 0/6] -no-user-config option, move CPU models to /usr/share
Date: Mon, 14 May 2012 10:04:27 -0500 [thread overview]
Message-ID: <4FB11EFB.3000700@codemonkey.ws> (raw)
In-Reply-To: <1335974850-30180-1-git-send-email-ehabkost@redhat.com>
On 05/02/2012 11:07 AM, Eduardo Habkost wrote:
> Changes v2 -> v3:
> - Actually change 'defconfig' type declaration to bool
> - Rebase against latest qemu.git (commit 563987d0a799f90b58a575b190a57546c335191b)
>
> Changes v1 -> v2:
> - Move qemu_read_default_config_files() prototype to qemu-config.h
> - Make defconfig and userconfig variable bool
> - Coding style change
>
> Patches 1 to 4 just move some code around, patch 5 just adds the new option
> without adding any new config file. Patch 6 finally creates a /usr/share/qemu
> /cpus-x86_64.conf file, with the CPU models we currently have on Qemu.
>
> Reference to previous discussion:
> - http://marc.info/?l=qemu-devel&m=133278877315665
Applied (as discussed prior to -rc0). Thanks.
Regards,
Anthony Liguori
>
>
> Eduardo Habkost (6):
> move code to read default config files to a separate function (v2)
> eliminate arch_config_name variable
> move list of default config files to an array
> vl.c: change 'defconfig' variable to bool (v2)
> implement -no-user-config command-line option (v3)
> move CPU definitions to /usr/share/qemu/cpus-x86_64.conf (v2)
>
> Makefile | 12 +++-
> arch_init.c | 32 ++++++++-
> arch_init.h | 2 -
> qemu-config.h | 4 +
> qemu-options.hx | 16 ++++-
> sysconfigs/target/cpus-x86_64.conf | 128 ++++++++++++++++++++++++++++++++++
> sysconfigs/target/target-x86_64.conf | 128 ----------------------------------
> vl.c | 18 ++---
> 8 files changed, 193 insertions(+), 147 deletions(-)
> create mode 100644 sysconfigs/target/cpus-x86_64.conf
>
prev parent reply other threads:[~2012-05-14 15:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 16:07 [Qemu-devel] [PATCH qemu v3 0/6] -no-user-config option, move CPU models to /usr/share Eduardo Habkost
2012-05-02 16:07 ` [Qemu-devel] [PATCH qemu 1/6] move code to read default config files to a separate function (v2) Eduardo Habkost
2012-05-02 16:07 ` [Qemu-devel] [PATCH qemu 2/6] eliminate arch_config_name variable Eduardo Habkost
2012-05-02 16:07 ` [Qemu-devel] [PATCH qemu 3/6] move list of default config files to an array Eduardo Habkost
2012-05-02 16:07 ` [Qemu-devel] [PATCH qemu 4/6] vl.c: change 'defconfig' variable to bool (v2) Eduardo Habkost
2012-05-02 16:07 ` [Qemu-devel] [PATCH qemu 5/6] implement -no-user-config command-line option (v3) Eduardo Habkost
2012-05-27 14:02 ` Andreas Färber
2012-05-28 6:35 ` Paolo Bonzini
2012-05-28 13:56 ` Andreas Färber
2012-05-02 16:07 ` [Qemu-devel] [PATCH qemu 6/6] move CPU definitions to /usr/share/qemu/cpus-x86_64.conf (v2) Eduardo Habkost
2012-05-11 13:34 ` [Qemu-devel] [PATCH qemu v3 0/6] -no-user-config option, move CPU models to /usr/share Eduardo Habkost
2012-05-11 13:37 ` Anthony Liguori
2012-05-11 13:42 ` Eduardo Habkost
2012-05-11 13:43 ` Jiri Denemark
2012-05-14 15:04 ` Anthony Liguori [this message]
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=4FB11EFB.3000700@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=ehabkost@redhat.com \
--cc=jdenemar@redhat.com \
--cc=libvir-list@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).