Power & Thermals

Microsoft made a point to focus on the Xbox One’s new power states during its introduction. Remember that when the Xbox 360 was introduced, power gating wasn’t present in any shipping CPU or GPU architectures. The Xbox One (and likely the PlayStation 4) can power gate unused CPU cores. AMD’s GCN architecture supports power gating, so I’d assume that parts of the GPU can be power gated as well. Dynamic frequency/voltage scaling is also supported. The result is that we should see a good dynamic range of power consumption on the Xbox One, compared to the Xbox 360’s more on/off nature.

AMD’s Jaguar is quite power efficient, capable of low single digit idle power so I would expect far lower idle power consumption than even the current slim Xbox 360 (50W would be easy, 20W should be doable for truly idle). Under heavy gaming load I’d expect to see higher power consumption than the current Xbox 360, but still less than the original 2005 Xbox 360.

Compared to the PlayStation 4, Microsoft should have the cooler running console under load. Fewer GPU ALUs and lower power memory don’t help with performance but do at least offer one side benefit.

OS
 

The Xbox One is powered by two independent OSes running on a custom version of Microsoft’s Hyper-V hypervisor. Microsoft made the hypervisor very lightweight, and created hard partitions of system resources for the two OSes that run on top of it: the Xbox OS and the Windows kernel.

The Xbox OS is used to play games, while the Windows kernel effectively handles all apps (as well as things like some of the processing for Kinect inputs). Since both OSes are just VMs on the same hypervisor, they are both running simultaneously all of the time, enabling seamless switching between the two. With much faster hardware and more cores (8 vs 3 in the Xbox 360), Microsoft can likely dedicate Xbox 360-like CPU performance to the Windows kernel while running games without any negative performance impact. Transitioning in/out of a game should be very quick thanks to this architecture. It makes a ton of sense.

Similarly, you can now multitask with apps. Microsoft enabled Windows 8-like multitasking where you can snap an app to one side of the screen while watching a video or playing a game on the other.

The hard partitioning of resources would be nice to know more about. The easiest thing would be to dedicate a Jaguar compute module to each OS, but that might end up being overkill for the Windows kernel and insufficient for some gaming workloads. I suspect ~1GB of system memory ends up being carved off for Windows.

Kinect & New Controller
 

All Xbox One consoles will ship with a bundled Kinect sensor. Game console accessories generally don’t do all that well if they’re optional. Kinect seemed to be the exception to the rule, but Microsoft is very focused on Kinect being a part of the Xbox going forward so integration here makes sense.

The One’s introduction was done entirely via Kinect enabled voice and gesture controls. You can even wake the Xbox One from a sleep state using voice (say “Xbox on”), leveraging Kinect and good power gating at the silicon level. You can use large two-hand pinch and stretch gestures to quickly move in and out of the One’s home screen.

The Kinect sensor itself is one of 5 semi-custom silicon elements in the Xbox One - the other four are: SoC, PCH, Kinect IO chip and Blu-ray DSP (read: the end of optical drive based exploits). In the One’s Kinect implementation Microsoft goes from a 640 x 480 sensor to 1920 x 1080 (I’m assuming 1080p for the depth stream as well). The camera’s field of view was increased by 60%, allowing support for up to 6 recognized skeletons (compared to 2 in the original Kinect). Taller users can now get closer to the camera thanks to the larger FOV, similarly the sensor can be used in smaller rooms.

The Xbox One will also ship with a new redesigned wireless controller with vibrating triggers:

Thanks to Kinect's higher resolution and more sensitive camera, the console should be able to identify who is gaming and automatically pair the user to the controller.

TV
 

The Xbox One features a HDMI input for cable TV passthrough (from a cable box or some other tuner with HDMI out). Content passed through can be viewed with overlays from the Xbox or just as you would if the Xbox wasn’t present. Microsoft built its own electronic program guide that allows you to tune channels by name, not just channel number (e.g. say “Watch HBO”). The implementation looks pretty slick, and should hopefully keep you from having to switch inputs on your TV - the Xbox One should drive everything. Microsoft appears to be doing its best to merge legacy TV with the new world of buying/renting content via Xbox Live. It’s a smart move.

One area where Microsoft is being a bit more aggressive is in its work with the NFL. Microsoft demonstrated fantasy football integration while watching NFL passed through to the Xbox One.

Memory Subsystem Final Words
Comments Locked

245 Comments

View All Comments

  • tipoo - Wednesday, May 22, 2013 - link

    That's one of the more interesting analogies for cache I've heard, lol. I've always used tomatoes in a store vs tomatoes in your kitchen.
  • BSMonitor - Wednesday, May 22, 2013 - link

    Sunday night season finale'.. Stewie rules!
  • MrPete123 - Wednesday, May 22, 2013 - link

    Curious about the "3 operating system" approach. You have Windows, XBox OS.....and Windows? Is the custom version of Hyper-V also running on Windows?
  • Spunjji - Wednesday, May 22, 2013 - link

    I think they're counting the hypervisor as an OS for explanatory purposes.
  • jeffkibuule - Wednesday, May 22, 2013 - link

    1) XBOX OS - plays games
    2) App OS - runs apps
    3) Hypervisor OS - based on Windows NT kernel, manages resources split between the two.

    Why 3? Why not just one? Likely because splitting them up improves portability of code from the XBOX ONE and Windows proper (Windows 8 and it's future versions).
  • MrPete123 - Wednesday, May 22, 2013 - link

    How do you know this?
  • takeship - Wednesday, May 22, 2013 - link

    The reason is, AFAIK, is that there are fundamental design issues with x86 that would allow third-parties, if given access to a direct OS - bare metal switch, the ability to hack the console in trivial amounts of time. XMBC, and the hacking that enabled it, is the primary reason why Microsoft went to PowerPC for the 360, so it only makes sense that coming back to x86 for the one, they need a "supervisor" of some sorts that prevents exploits on the bare-metal x86 side from being carried back over to the "full-fat" OS side.
  • Kevin G - Wednesday, May 22, 2013 - link

    The PPC in the Xbox 360 supports virtualization. This isn't a reason to ditch PPC in favor of x86.

    The big reason is due to AMD's HSA support with their GPU's.
  • Jaybus - Wednesday, May 22, 2013 - link

    No. Both Windows and XBox OS run on Hyper-V. Hyper-V is the only OS (known as a hypervisor) running on the bare metal.
  • BSMonitor - Wednesday, May 22, 2013 - link

    @Anand ~ In regard to x86 and backward game compatibility... All XBox Live game content currently available would be incompatible with Xbox One?? Am mainly talking the downloadable stuff, i.e. Castle Crashers or TMNT Arcade game??

Log in

Don't have an account? Sign up now