RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

    Case entered as a placeholder.  Currently proposed upstream changes in
    cpuid data for AMD cpus may need to be represented in both upstream
    and rhel6 cpu model config definitions pending outcome.  Ref:

    http://linux.derkeiler.com/Mailing-Lists/Kernel/2010-09/msg02234.html

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Moving content of this bug to 632257 as it is related, more general,
and requires the same testing treatment.]

*** This bug has been marked as a duplicate of bug 632257 ***

Ugh.  Reopening this as after further consideration the associated
upstream AMD cpu feature changes don't impact current models and
don't constitute an issue for 6.1.  Support of them is almost
certain to be a future issue so here is a synopsis of what is
needed thus far:

8000_0001:ecx 1<<11  XOP
8000_0001:ecx 1<<15  LWP
8000_0001:ecx 1<<16  FMA4
8000_0001:ecx 1<<21  TMB
8000_0001:ecx 1<<22  TOPOEXT

0000_0001:ecx 1<<25  AES

[the following are more complex to address as the current qemu feature
flags scheme does not address Fn8000_000A as model configurable]

8000_000A:edx 1<<4  TSCRATEMSR
8000_000A:edx 1<<5  VMCBCLEAN
8000_000A:edx 1<<6  FLUSHBYASID
8000_000A:edx 1<<7  DECODEASSISTS
8000_000A:edx 1<<10  PAUSEFILTER
8000_000A:edx 1<<11  PFTHRESHOLD

This also best pushed upstream along with new AMD
models requiring these feature flags.