All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Eduardo Habkost" <eduardo@habkost.net>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Subject: x86 CPU properties "family", "model", "stepping", "tsc-freq"
Date: Wed, 09 Oct 2024 13:01:40 +0200	[thread overview]
Message-ID: <87wmihr14b.fsf@pond.sub.org> (raw)

QOM properties serve several purposes: initial configuration (external
interface), run time control and monitoring (external interface), and
internal purposes like versioning.  Which purpose(s) a property serves
is often unclear.

The x86 CPU properties "family", "model", and "stepping" are used
internally; see target/i386/cpu.c and hw/i386/pc.c.  I figure changing
them at run time makes no sense.  What about configuration?  Can the
user set arbitrary CPU properties?  If yes, are these properties meant
to be set by the user?

Property "tsc-freq" seems not to be used internally.  I figure changing
it at run time makes no sense.  Looks like it is be meant to be set by
the user: x86_cpu_parse_featurestr() seems to parse it from the argument
of -cpu.  Correct?  Note that -cpu help doesn't mention it.



             reply	other threads:[~2024-10-09 11:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 11:01 Markus Armbruster [this message]
2024-10-09 11:35 ` x86 CPU properties "family", "model", "stepping", "tsc-freq" Daniel P. Berrangé
2024-10-09 11:47   ` Markus Armbruster
2024-10-09 13:44   ` Markus Armbruster
2024-10-09 13:47     ` Daniel P. Berrangé

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=87wmihr14b.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.