All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dor Laor <dlaor@redhat.com>
To: Jun Koi <junkoi2004@gmail.com>
Cc: Sasha Levin <levinsasha928@gmail.com>,
	kvm@vger.kernel.org, Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: -cpu core2duo still has no SSE4 support?
Date: Thu, 15 Sep 2011 12:19:14 +0300	[thread overview]
Message-ID: <4E71C312.1020908@redhat.com> (raw)
In-Reply-To: <CA+g7VZ0eLSHcOE1XCJCebW-UxQLqhwKKnSTLTow8-H0oSheVbw@mail.gmail.com>

On 09/15/2011 12:14 PM, Jun Koi wrote:
> On Thu, Sep 15, 2011 at 5:05 PM, Sasha Levin<levinsasha928@gmail.com>  wrote:
>> On Thu, 2011-09-15 at 17:04 +0800, Jun Koi wrote:
>>> hi,
>>>
>>> i run kvm with "-cpu core2duo" option, but /proc/cpuinfo only shows
>>> SSE and SSE2.
>>> my host is Core i7, so i suppose that i should have SSE4 with this
>>> option, but it seems not?
>>>
>>> is there any way to get SSE4?
>>
>> How about just running it with '-cpu host'?
>
> hah, that works, thanks!
>
> but then there are 2 problems:
>
> - "-cpu host" should be exposed in the doc. "kvm -cpu ?" reports no
> such option, so i missed it.
> - "-cpu core2duo" should enable SSE4, but it doesnt. a bug?

If this model should have contain it, yes.
According to sysconfigs/target/target-x86_64.conf  it shouldn't be in 
core2duo but does appear in newer ones.

>
> thanks,
> Jun
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2011-09-15  9:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-15  9:04 -cpu core2duo still has no SSE4 support? Jun Koi
2011-09-15  9:05 ` Sasha Levin
2011-09-15  9:14   ` Jun Koi
2011-09-15  9:19     ` Dor Laor [this message]
2011-09-15  9:27     ` Sasha Levin

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=4E71C312.1020908@redhat.com \
    --to=dlaor@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=junkoi2004@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    /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.