From: Amit Shah <amit.shah@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/12] cpuid: cleanup and some enhancements
Date: Fri, 11 Sep 2009 13:25:35 +0530 [thread overview]
Message-ID: <20090911075535.GF31399@amit-x200.redhat.com> (raw)
In-Reply-To: <1252621257-26364-1-git-send-email-andre.przywara@amd.com>
On (Fri) Sep 11 2009 [00:20:45], Andre Przywara wrote:
> Hi,
>
> the following patchset cleans up CPUID bit handling and adds some smaller
> features.
> The most prominent change is to move all CPUID related functions to a
> separate file. About 40% of helper.c was actually CPUID related, so say
> hello to cpuid.c. While at it, I fixed some formatting issues. (Patch 1-5)
> Patch 6 & 7 add the CPUID feature flag names to the output of -cpu ?.
> Patch 8 & 9 simplify some code.
> Patch 10 allows more CPUID leafs to be propagated to guests when -cpu host
> is used, this should now reflect the host CPU's cache size.
> Patch 11 adds a trimming feature (similar to KVM) to QEMU/TCG. The goal
> is to describe CPU models more precisely by reflecting the feature bits of
> the real hardware. Features that QEMU does not support are then masked.
> If we add features to QEMU, we only need to adjust it in one location.
> I will send a patch fixing the CPU models later.
> Patch 12 adjusts the size of the L2 cache described by leaf 4 to a more
> conservative value of one megabyte. This prevents guests assuming too large
> caches if they use optimized algorithms.
>
> Please review, comment and apply!
Looks like a good series!
> Thanks and Regards,
> Andre.
Amit
next prev parent reply other threads:[~2009-09-11 7:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 22:20 [Qemu-devel] [PATCH 0/12] cpuid: cleanup and some enhancements Andre Przywara
2009-09-10 22:20 ` [Qemu-devel] [PATCH 01/12] cpuid: move CPUID functions into separate file Andre Przywara
2009-09-10 22:20 ` [Qemu-devel] [PATCH 02/12] cpuid: fix over-long lines Andre Przywara
2009-09-10 22:20 ` [Qemu-devel] [PATCH 03/12] cpuid: replace magic number with named constant Andre Przywara
2009-09-10 22:20 ` [Qemu-devel] [PATCH 04/12] cpuid: fix comments Andre Przywara
2009-09-10 22:20 ` [Qemu-devel] [PATCH 05/12] cpuid: moved host_cpuid function and remove prototype Andre Przywara
2009-09-10 22:20 ` [Qemu-devel] [PATCH 06/12] cpuid: add missing CPUID feature flag names Andre Przywara
2009-09-10 22:20 ` [Qemu-devel] [PATCH 07/12] cpuid: list all known x86 CPUID feature flags Andre Przywara
2009-09-10 22:20 ` [Qemu-devel] [PATCH 08/12] cpuid: remove unnecessary kvm_trim function Andre Przywara
2009-09-10 22:20 ` [Qemu-devel] [PATCH 09/12] cpuid: simplify CPUID flag search function Andre Przywara
2009-09-11 7:55 ` Amit Shah
2009-09-11 19:30 ` Andre Przywara
2009-09-14 7:23 ` Amit Shah
2009-09-10 22:20 ` [Qemu-devel] [PATCH 10/12] cpuid: propagate further CPUID leafs when -cpu host Andre Przywara
2009-09-10 22:20 ` [Qemu-devel] [PATCH 11/12] cpuid: add TCG feature bit trimming Andre Przywara
2009-09-10 22:20 ` [Qemu-devel] [PATCH 12/12] cpuid: decrease L2 cache for Intel and add comments Andre Przywara
2009-09-11 7:55 ` Amit Shah [this message]
2009-09-14 17:08 ` [Qemu-devel] [PATCH 0/12] cpuid: cleanup and some enhancements Anthony Liguori
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=20090911075535.GF31399@amit-x200.redhat.com \
--to=amit.shah@redhat.com \
--cc=andre.przywara@amd.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).