From: Antti Louko <alo@louko.com>
To: xen-devel@lists.xensource.com
Cc: kuiliang.shi@intel.com
Subject: Re: VMX status report Nov.18 changset 7870
Date: Fri, 18 Nov 2005 15:13:18 +0200 [thread overview]
Message-ID: <opr79e85g1.wl@alo99.louko.com> (raw)
In-Reply-To: <opu0ea85qo.wl@alo99.louko.com>
One further question. I just wonder if 662 and 672 are really
different to 660 and 670 or is this just the matter of microcode
update or some other magic? This would explain the need for the
special BIOS.
next prev parent reply other threads:[~2005-11-18 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 13:06 VMX status report Nov.18 changset 7870 Antti Louko
2005-11-18 13:13 ` Antti Louko [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-18 5:27 Shi, Kuiliang
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=opr79e85g1.wl@alo99.louko.com \
--to=alo@louko.com \
--cc=kuiliang.shi@intel.com \
--cc=xen-devel@lists.xensource.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.