I had some questions about the source: What is the expected behavior of the "is_launched" function on non-TXT platforms?
"is_launched" is a wrapper function which calls "txt_is_launched" which reads the TXT.STS configuration register. At multiple locations, tboot attempts to read TXT configuration registers without confirming that the system is a TXT-enabled processor or chipset. I noticed that this was not the case in the tboot code on much earlier versions of tboot. I am looking at how tboot behaves on an AMD system . Based on what I saw in my kernel's dmesg output, the 0xfed30000 physical addresses are not defined in the E820 map. I made minor modifications to the tboot code and noticed that in both the "begin_launch" and "shutdown" functions where "is_launched" is called, "is_launched" is returning true. I am wondering if the "is_launched" function is absolutely necessary in the locations I mentioned and if there is a way around it. Thanks, Safayet ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ tboot-devel mailing list tboot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tboot-devel
