From: Dan Kenigsberg <danken@qumranet.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Allow setting the vendor_id string with x86's -cpu option
Date: Sun, 9 Dec 2007 15:52:01 +0200 [thread overview]
Message-ID: <20071209135201.GA5113@karma.qumranet.com> (raw)
In-Reply-To: <200712091136.36900.paul@codesourcery.com>
On Sun, Dec 09, 2007 at 11:36:34AM +0000, Paul Brook wrote:
> > + x86_cpu_def->vendor1 = cpu_to_le32(*(uint32_t *)val);
> > + x86_cpu_def->vendor2 = cpu_to_le32(*(uint32_t *)(val +
> > 4)); + x86_cpu_def->vendor3 = cpu_to_le32(*(uint32_t *)(val
>
> Still not good enough. val might not be aligned.
>
So, is it that my only hope is going back to basics?
diff --git a/target-i386/helper2.c b/target-i386/helper2.c
index 67658e2..2ef4be3 100644
--- a/target-i386/helper2.c
+++ b/target-i386/helper2.c
@@ -254,6 +254,18 @@ static int cpu_x86_find_by_name(x86_def_t *x86_cpu_def, const char *cpu_model)
goto error;
}
x86_cpu_def->stepping = stepping;
+ } else if (!strcmp(featurestr, "vendor")) {
+ if (strlen(val) != 12) {
+ fprintf(stderr, "vendor string must be 12 chars long\n");
+ x86_cpu_def = 0;
+ goto error;
+ }
+ x86_cpu_def->vendor1 = val[0] + (val[1] << 8)
+ + (val[2] << 16) + (val[3] << 24);
+ x86_cpu_def->vendor2 = val[4] + (val[5] << 8)
+ + (val[6] << 16) + (val[7] << 24);
+ x86_cpu_def->vendor3 = val[8] + (val[9] << 8)
+ + (val[10] << 16) + (val[11] << 24);
} else {
fprintf(stderr, "unrecognized feature %s\n", featurestr);
x86_cpu_def = 0;
next prev parent reply other threads:[~2007-12-09 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-25 13:23 [Qemu-devel] [PATCH] Allow setting the vendor_id string with x86's -cpu option Dan Kenigsberg
2007-12-09 3:02 ` Thiemo Seufer
2007-12-09 9:27 ` Dan Kenigsberg
2007-12-09 11:36 ` Paul Brook
2007-12-09 13:52 ` Dan Kenigsberg [this message]
2007-12-09 18:29 ` Andreas Schwab
2007-12-09 18:58 ` Dan Kenigsberg
2007-12-09 20:00 ` Dan Kenigsberg
2007-12-20 16:40 ` [Qemu-devel] [PATCH] Allow setting the vendor and model_id strings " Dan Kenigsberg
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=20071209135201.GA5113@karma.qumranet.com \
--to=danken@qumranet.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).