<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US"><title type="html">Glass House</title><subtitle type="html">News and commentary on Windows Embedded Operating Systems. </subtitle><id>http://blogs.msdn.com/mglass/atom.xml</id><link rel="alternate" type="text/html" href="http://blogs.msdn.com/mglass/default.aspx" /><link rel="self" type="application/atom+xml" href="http://blogs.msdn.com/mglass/atom.xml" /><generator uri="http://communityserver.org" version="2.1.61025.2">Community Server</generator><updated>2008-02-25T09:47:00Z</updated><entry><title>Hypervisors in Embedded Systems</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/mglass/archive/2008/03/04/hypervisors-in-embedded-systems.aspx" /><id>http://blogs.msdn.com/mglass/archive/2008/03/04/hypervisors-in-embedded-systems.aspx</id><published>2008-03-04T03:07:00Z</published><updated>2008-03-04T03:07:00Z</updated><content type="html">&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt"&gt;&lt;FONT face=Calibri size=3&gt;I attended Embedded World in Nurnberg last week. The number one application I saw over and over again was for embedded devices based on multi-core processors. If you think of Microsoft’s entire range of embedded operating systems – Micro-framework at the low end, Windows CE (the only real-time OS (RTOS)), and Windows XP Embedded; I expect multi-core processors to target systems built for Windows XP Embedded (XPe) first. This is because the cost of a multi-core processor is higher than a single-core and at least for now more likely in systems that can absorb the cost of an XPe client. But the interesting twist is that the value of multiple cores is that you can run an RTOS in one or more cores and run XPe in other cores. XPe would be used to run Windows applications – say some kind of Human Machine interface (HMI), where the RTOS would run a factory control application that requires a guarantee of a processor’s time slice at some frequency that only Windows CE could deliver (or RTOS competitors like WindRiver’s VxWorks or a custom Linux solution). &lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt"&gt;&lt;FONT face=Calibri size=3&gt;In order to make this work, there has to be a piece of software that loads an OS into one or more cores and virtualizes hardware access of common components. This virtualization software is called a hypervisor and is often in the form of a boot loader. The boot loader would load one or more operating systems into cores and then leave its tiny run-time (as small as 20kbytes) to handle hardware interrupts to facilitate virtualization (sharing or multiplexing between cores). The effectiveness of a hypervisor is measured inversely by the size of its memory footprint and any latency it adds. &lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt"&gt;&lt;FONT face=Calibri size=3&gt;Although the systems we saw demoed in Embedded World were all Intel multi-core processors, SH and Arms (processors supported by Windows CE) are rumored to be working on multi-core products. I see the trend to multi-core processing and hypervisors a real opportunity for XPe and maybe later a Vista-based embedded OS as these can be paired with an RTOS to qualify them to a broader range of applications in manufacturing automation.&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt"&gt;&lt;FONT face=Calibri size=3&gt;Hypervisors also play an important role in thin client strategies, but that discussion is for another blog post. &lt;/FONT&gt;&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8013203" width="1" height="1"&gt;</content><author><name>mglassms</name><uri>http://blogs.msdn.com/members/mglassms.aspx</uri></author><category term="Windows Embedded" scheme="http://blogs.msdn.com/mglass/archive/tags/Windows+Embedded/default.aspx" /><category term="Windows CE" scheme="http://blogs.msdn.com/mglass/archive/tags/Windows+CE/default.aspx" /><category term="Windows XP Embedded" scheme="http://blogs.msdn.com/mglass/archive/tags/Windows+XP+Embedded/default.aspx" /></entry><entry><title>EMIC - Aachen, Germany</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/mglass/archive/2008/02/25/emic-aachen-germany.aspx" /><id>http://blogs.msdn.com/mglass/archive/2008/02/25/emic-aachen-germany.aspx</id><published>2008-02-25T12:47:00Z</published><updated>2008-02-25T12:47:00Z</updated><content type="html">&lt;P&gt;In&amp;nbsp;Aachen for meetings at the European Microsoft Innovation Center (EMIC). Just enjoyed a demo of a cell phone connecting to a laptop via bluetooth to access a home server over the internet for media. Very cool work here. Can't wait to see the next two sessions. &lt;/P&gt;
&lt;P&gt;EMIC works on embedded applications and is ramping up a new team to work directly with the Windows Embedded Team in Redmond. &lt;/P&gt;
&lt;P&gt;&lt;A class="" href="http://blogs.msdn.com/mikehall" target=_blank mce_href="http://blogs.msdn.com/mikehall"&gt;Mike Hall&lt;/A&gt;, Chris Muench and I are on our way to embedded world in Nurnberg starting with this two-day meeting with EMIC and filled with several customer visits (including Siemens on Friday). &lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=7891018" width="1" height="1"&gt;</content><author><name>mglassms</name><uri>http://blogs.msdn.com/members/mglassms.aspx</uri></author><category term="Windows Embedded" scheme="http://blogs.msdn.com/mglass/archive/tags/Windows+Embedded/default.aspx" /><category term="Windows XP Embedded" scheme="http://blogs.msdn.com/mglass/archive/tags/Windows+XP+Embedded/default.aspx" /></entry></feed>