From: Craig Metz <cmetz@inner.net>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, andreas.tanz@kvt.de
Subject: Re: KVM on Via Nano (Isaiah) CPUs?
Date: Fri, 08 May 2009 15:16:32 -0400 [thread overview]
Message-ID: <20090509041641.77B58582C@rmail.inner.net> (raw)
In-Reply-To: Your message of "Wed, 01 Apr 2009 19:30:35 +0300." <49D396AB.6090304@redhat.com>
In message <49D396AB.6090304@redhat.com>, you write:
>Via engineers have contacted me and confirmed that this is a problem in
>the processor.
Is there a known-fixed CPU revision?
Is there a way to identify working vs. non-working chips, either from IC
stamp or from /proc/cpuinfo? (Bonus: is it possible to put a check and an error
into the kvm-intel kernel model?)
Thanks,
-Craig
next prev parent reply other threads:[~2009-05-08 23:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 13:45 KVM on Via Nano (Isaiah) CPUs? Craig Metz
2009-04-01 16:30 ` Avi Kivity
2009-05-08 19:16 ` Craig Metz [this message]
2009-05-09 9:32 ` Avi Kivity
2009-05-12 6:48 ` KVM on Via Nano (Isaiah) CPUs? <Virus checked> Andreas Tanz
2009-05-12 6:50 ` Avi Kivity
2009-04-01 20:04 KVM on Via Nano (Isaiah) CPUs? Jesse Ahrens
2009-04-02 9:08 ` Oliver Rath
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=20090509041641.77B58582C@rmail.inner.net \
--to=cmetz@inner.net \
--cc=andreas.tanz@kvt.de \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.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).