qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Don Slutz <Don@CloudSwitch.Com>, Igor Mammedov <imammedo@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Anthony Liguori <anthony@codemonkey.ws>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/7] move CPU models from cpus-x86_64.conf to C
Date: Mon, 10 Sep 2012 16:58:39 +0200	[thread overview]
Message-ID: <504E001F.80509@suse.de> (raw)
In-Reply-To: <504DFE4E.4030106@CloudSwitch.Com>

Am 10.09.2012 16:50, schrieb Don Slutz:
> On 09/10/12 09:04, Igor Mammedov wrote:
>> But question unrelated to this patch is still stand if ia64 is valid
>> bit for
>> 01.EDX[30]?
>>
>>
> Intel® Processor Identification
> and the CPUID Instruction
> Application Note 485
> January 2006
> 
> Order Number: 241618-030
> 
> ...
> 
> Updated Table 3-5 to include the feature flag definition (EDX[30]) for
> IA64 capabilities.
> ...
> 30 IA64 IA64 Capabilities The processor is a member of the Intel®
> Itanium® processor family
>                            and currently operating in IA32 emulation mode.
> 
> ---------------
> 
> Says that it is. Along with http://en.wikipedia.org/wiki/CPUID and
> http://www.sandpile.org/x86/cpuid.htm#level_0000_0001h (IA-64)

Don't those semantics contradict the use in qemu-system-x86_64 or
qemu-system-i386 rather than qemu-system-ia64 then? We don't model ia64
CPUs here (just like we don't model ppc64 CPUs in ppc) so the flag could
never become 1 IIUC.

Andreas

> But the newest version I found (241618-037, January 2011) is back to
> Reserved.
> 
> 
>    -Don Slutz

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2012-09-10 14:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05 20:41 [Qemu-devel] [PATCH 0/7] x86 CPU patches that didn't get into 1.2 Eduardo Habkost
2012-09-05 20:41 ` [Qemu-devel] [PATCH 1/7] target-i386: Fold -cpu ?cpuid, ?model output into -cpu help, drop ?dump Eduardo Habkost
2012-09-10  9:40   ` Igor Mammedov
2012-09-05 20:41 ` [Qemu-devel] [PATCH 2/7] Drop cpu_list_id macro Eduardo Habkost
2012-09-10  9:46   ` Igor Mammedov
2012-09-05 20:41 ` [Qemu-devel] [PATCH 3/7] i386: add missing CPUID_* constants Eduardo Habkost
2012-09-10  9:57   ` Igor Mammedov
2012-09-05 20:41 ` [Qemu-devel] [PATCH 4/7] move CPU models from cpus-x86_64.conf to C Eduardo Habkost
2012-09-10 12:18   ` Igor Mammedov
2012-09-10 12:31     ` Igor Mammedov
2012-09-10 13:04       ` Igor Mammedov
2012-09-10 14:50         ` Don Slutz
2012-09-10 14:58           ` Andreas Färber [this message]
2012-09-10 15:07             ` Eduardo Habkost
2012-09-10 15:13               ` Andreas Färber
2012-09-10 15:04         ` Eduardo Habkost
2012-09-10 13:40   ` Igor Mammedov
2012-09-11 19:45     ` Don Slutz
2012-09-05 20:41 ` [Qemu-devel] [PATCH 5/7] eliminate cpus-x86_64.conf file Eduardo Habkost
2012-09-10 13:46   ` Igor Mammedov
2012-09-05 20:41 ` [Qemu-devel] [PATCH 6/7] x86_cpudef_setup: coding style change Eduardo Habkost
2012-09-11 19:45   ` Don Slutz
2012-09-05 20:41 ` [Qemu-devel] [PATCH 7/7] i386: kill cpudef config section support Eduardo Habkost
2012-09-10 14:20   ` Igor Mammedov
2012-09-10 15:17 ` [Qemu-devel] [PATCH 0/7] x86 CPU patches that didn't get into 1.2 Andreas Färber
2012-09-10 15:30   ` Igor Mammedov
2012-09-10 15:46   ` [Qemu-devel] CPU code roadmap (was Re: [PATCH 0/7] x86 CPU patches that didn't get into 1.2) Eduardo Habkost
2012-09-11 14:59     ` Eduardo Habkost
2012-09-17 17:29 ` [Qemu-devel] [PATCH 0/7] x86 CPU patches that didn't get into 1.2 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=504E001F.80509@suse.de \
    --to=afaerber@suse.de \
    --cc=Don@CloudSwitch.Com \
    --cc=anthony@codemonkey.ws \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).