qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrogg@gmail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: n270 SSSE3 flag problem
Date: Mon, 27 Oct 2008 20:30:32 +0100	[thread overview]
Message-ID: <fb249edb0810271230m1a069c6fl89630743e385c77c@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580810271158s33173030g791c86fd1ab1d09@mail.gmail.com>

2008/10/27 Blue Swirl <blauwirbel@gmail.com>:
> 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 */

Thanks, good catch!  I had only tested n270 in user mode, that's why
it didn't blow up.

Cheers

      parent reply	other threads:[~2008-10-27 19:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-27 18:58 [Qemu-devel] n270 SSSE3 flag problem Blue Swirl
2008-10-27 19:10 ` Laurent Desnogues
2008-10-27 19:30 ` andrzej zaborowski [this message]

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=fb249edb0810271230m1a069c6fl89630743e385c77c@mail.gmail.com \
    --to=balrogg@gmail.com \
    --cc=blauwirbel@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).