From: "Blue Swirl" <blauwirbel@gmail.com>
To: andrzej zaborowski <balrogg@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] n270 SSSE3 flag problem
Date: Mon, 27 Oct 2008 20:58:22 +0200 [thread overview]
Message-ID: <f43fc5580810271158s33173030g791c86fd1ab1d09@mail.gmail.com> (raw)
Hi,
Sparse detected a problem with n270 CPU definition, I think
.ext_features = CPUID_EXT_MONITOR |
CPUID_EXT_SSE3 /* PNI */, CPUID_EXT_SSSE3,
/* Missing: CPUID_EXT_DSCPL | CPUID_EXT_EST |
* CPUID_EXT_TM2 | CPUID_EXT_XTPR */
should be:
.ext_features = CPUID_EXT_MONITOR |
CPUID_EXT_SSE3 /* PNI */ | CPUID_EXT_SSSE3,
/* Missing: CPUID_EXT_DSCPL | CPUID_EXT_EST |
* CPUID_EXT_TM2 | CPUID_EXT_XTPR */
next reply other threads:[~2008-10-27 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 18:58 Blue Swirl [this message]
2008-10-27 19:10 ` [Qemu-devel] n270 SSSE3 flag problem Laurent Desnogues
2008-10-27 19:30 ` [Qemu-devel] " andrzej zaborowski
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=f43fc5580810271158s33173030g791c86fd1ab1d09@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=balrogg@gmail.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).