All of lore.kernel.org
 help / color / mirror / Atom feed
From: David <xendev@bsdlazarus.com>
To: Goetz Bock <bock@blacknet.de>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: VMX Hardware
Date: Mon, 15 Aug 2005 22:36:54 -0400	[thread overview]
Message-ID: <43015146.8070508@bsdlazarus.com> (raw)
In-Reply-To: <20050814104441.GJ8146@shell.blacknet.de>

Hi,

 > Looking at Intels latest 'upgrade' path, which shows we'll often have 
to buy new HW for new cpu's, I'd go for AMD.
 > Seems they're into the game of longtime support, so my bet is that 
you'll be able to outfit quite a lot of the latest mobos with future 
AMD64 cpu's.
 > This has of late been the case with i.e. their X2 line. Most resent 
mobos can handle those with a BIOS upgrade.
 > I'd be looking at Iwill, Tyan, Gigabye.
 >

This is conjecture, nor am I well versed in this technology, so take 
this with a grain of salt.

I would assuume that both Intel and AMD platforms will need a new 
mainboard for the switch to hardware VM tech...

Why?

Intel: If only beacsue if the external memory controller, seemingly they 
Intel will need a new chipset.  I also don't see Intel passing on an 
oportuniity to sell more chipsets.

AMD:  With AMD planning to rollout support for DDR-2 and sockets M2/F, 
it is unlikely that hardware VM tech will be back-ported to the current 
generation A64 platform.

-- David

      parent reply	other threads:[~2005-08-16  2:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-14 10:44 VMX Hardware Goetz Bock
2005-08-14 11:09 ` Keir Fraser
2005-08-14 12:23   ` Re: [Xen-devel] " Mogens Valentin
2005-08-14 13:27     ` [Xen-users] " Keir Fraser
2005-08-14 18:09       ` Re: [Xen-devel] " Anthony Liguori
2005-08-14 18:23         ` [Xen-users] " Keir Fraser
2005-08-16  2:36 ` David [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=43015146.8070508@bsdlazarus.com \
    --to=xendev@bsdlazarus.com \
    --cc=bock@blacknet.de \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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.