Menu
▾
▴
tboot-devel — Developer support
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(13) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(19) |
Feb
(24) |
Mar
(8) |
Apr
(14) |
May
(8) |
Jun
(10) |
Jul
(14) |
Aug
(3) |
Sep
(13) |
Oct
(27) |
Nov
(39) |
Dec
(24) |
| 2009 |
Jan
(19) |
Feb
(4) |
Mar
(2) |
Apr
(15) |
May
|
Jun
(2) |
Jul
(44) |
Aug
(21) |
Sep
(20) |
Oct
(2) |
Nov
(1) |
Dec
(7) |
| 2010 |
Jan
(7) |
Feb
(10) |
Mar
(2) |
Apr
(12) |
May
(7) |
Jun
(2) |
Jul
(18) |
Aug
(11) |
Sep
(4) |
Oct
(25) |
Nov
(8) |
Dec
(1) |
| 2011 |
Jan
(27) |
Feb
(2) |
Mar
(19) |
Apr
(8) |
May
(16) |
Jun
(11) |
Jul
(9) |
Aug
(9) |
Sep
(35) |
Oct
(9) |
Nov
(8) |
Dec
(32) |
| 2012 |
Jan
(37) |
Feb
(20) |
Mar
(2) |
Apr
(24) |
May
(4) |
Jun
(3) |
Jul
(5) |
Aug
(21) |
Sep
(8) |
Oct
(15) |
Nov
(1) |
Dec
(7) |
| 2013 |
Jan
(4) |
Feb
(8) |
Mar
(38) |
Apr
(9) |
May
(42) |
Jun
(4) |
Jul
(21) |
Aug
(4) |
Sep
|
Oct
(7) |
Nov
(2) |
Dec
(3) |
| 2014 |
Jan
(8) |
Feb
(8) |
Mar
(5) |
Apr
(9) |
May
(19) |
Jun
(1) |
Jul
(10) |
Aug
(25) |
Sep
(6) |
Oct
(2) |
Nov
(5) |
Dec
(1) |
| 2015 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
(12) |
Jun
|
Jul
(2) |
Aug
(5) |
Sep
(11) |
Oct
(5) |
Nov
(3) |
Dec
(1) |
| 2016 |
Jan
(2) |
Feb
(24) |
Mar
|
Apr
(6) |
May
(26) |
Jun
(20) |
Jul
(8) |
Aug
(15) |
Sep
(21) |
Oct
(1) |
Nov
(7) |
Dec
(24) |
| 2017 |
Jan
(12) |
Feb
(2) |
Mar
(6) |
Apr
(8) |
May
(18) |
Jun
(13) |
Jul
(12) |
Aug
(8) |
Sep
(5) |
Oct
(1) |
Nov
|
Dec
|
| 2018 |
Jan
(2) |
Feb
(12) |
Mar
(8) |
Apr
(5) |
May
(7) |
Jun
(1) |
Jul
(4) |
Aug
(8) |
Sep
(2) |
Oct
(3) |
Nov
(4) |
Dec
(3) |
| 2019 |
Jan
(8) |
Feb
|
Mar
(2) |
Apr
|
May
(3) |
Jun
(4) |
Jul
(1) |
Aug
|
Sep
(8) |
Oct
(6) |
Nov
(20) |
Dec
(14) |
| 2020 |
Jan
(25) |
Feb
(12) |
Mar
(2) |
Apr
(13) |
May
(44) |
Jun
(9) |
Jul
|
Aug
(3) |
Sep
(5) |
Oct
(4) |
Nov
(2) |
Dec
|
| 2021 |
Jan
(6) |
Feb
|
Mar
(7) |
Apr
(1) |
May
|
Jun
(2) |
Jul
|
Aug
(16) |
Sep
(4) |
Oct
(6) |
Nov
(1) |
Dec
(6) |
| 2022 |
Jan
(5) |
Feb
(4) |
Mar
(22) |
Apr
(6) |
May
(4) |
Jun
(17) |
Jul
(2) |
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(2) |
| 2023 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2024 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
|
From: Wang, S. <sha...@in...> - 2008-11-18 05:55:03
|
What do you mean of "late launch"? I assume it should not be "post launch". Shane Lil Evil wrote: > Hi, > > I was wondering whats the status and/or roadmap for late launch with > tboot, as I was looking at getting some kind of late launch to work? > I do believe some people on this mailing list are working on a late > launch proof of concept? > What's the status there? > > > thanks > lIl |
|
From: Ross P. <Ros...@ci...> - 2008-11-16 22:43:13
|
I think I found a bug in the command line handling code in tboot. It is in the calls to cmdline_option_read() in lib.c. This function uses the ARRAY_SIZE macro within the loop but in this case it is being used with the cmdline_option_t *cmdline_option argument which is a pointer. The ARRAY_SIZE macro evaluates sizeof() on the pointer which is 4 in this case and the loop never runs. I wanted a sanity check on this but I think it is a problem. I checked the other places that ARRAY_SIZE is used and they seem OK. I discovered this while working on changes to tboot logging. I can fix it in the patch I hope to send out early next week if that works. Thanks Ross Ross Philipson Senior Software Engineer Citrix Systems, Inc 14 Crosby Drive Bedford, MA 01730 781-301-7949 ros...@ci... <mailto:ros...@ci...> |
|
From: Ross P. <Ros...@ci...> - 2008-11-15 20:37:15
|
I was going to start adding support for configuring the various logging methods and configurations in tboot. Joe, were you planning on keeping the existing command line parsing code as it is in tboot/common/lib.c? If so I will use the framework to add the various logging settings. Also memory and vga logging are already present but just not really used. One thing I will do is unify the logging/tracing to include these methods. Thanks Ross From: Cihula, Joseph [mailto:jos...@in...] Sent: Wednesday, November 12, 2008 4:27 AM To: Ross Philipson; tbo...@li... Subject: RE: Enhance serial support in tboot I've been giving some thought to this and I think that it would be valuable to have a command line parameter that allowed specifying how logging is done: VGA, memory, serial (and any combination of them or lack of them). The serial parameter would also need to support specifying the various serial configs . I've been holding off on this because I wanted to limit the amount of command line options since the command line is not currently part of the measurement of tboot, and thus there is a greater potential for malicious manipulation of the code via command line. E.g. if by adding more command line options one of them introduces a buffer overflow then there would be no way to determine if a given invocation of tboot was done with such a malicious command line. But I think that it is time to bite the bullet and add the command line to the tboot measurement. So with that support, making the command line more complex will be less risky. I'll take care of the command line measurement changes, but I would welcome patches for the above logging support. Joe P.S. Back from vacation now so emails should be more timely. From: Ross Philipson [mailto:Ros...@ci...] Sent: Monday, November 03, 2008 11:14 AM To: tbo...@li... Subject: [tboot-devel] Enhance serial support in tboot I have recently been working on laptops that do not have serial ports so I have been using an ExpressCard serial adapter. I had to make modification to tboot to use a different IO port and clock frequency. I have found that having serial debug output for tboot is incredibly valuable during development. The Xen console driver (on which the tboot early_printk is loosely based as it seems) allows serial console configuration with command line arguments (including setting the clock freq. now). I was thinking of pulling this into tboot but I wanted to see if the community thought this was something valuable to do - something that could be incorporated in tboot? Thanks Ross Ross Philipson Senior Software Engineer Citrix Systems, Inc 14 Crosby Drive Bedford, MA 01730 781-301-7949 ros...@ci... |
|
From: Karthik . <tr...@gm...> - 2008-11-12 22:36:18
|
One of the cases where Tboot hangs is when you have any USB device (drive, keyboard, mouse) plugged in. So to avoid this you need to remove any USB key attached, during Tboot loading process and can plug it back once you are in the OS. HP is working with its vendor to resolve this issue and an Engineering Advisory will soon be posted on its website addressing this issue. Thanks Karthik On Mon, Nov 10, 2008 at 4:02 PM, Ross Philipson <Ros...@ci...> wrote: > I am using F.0B - the latest publically available for those systems. > Tboot executes GETSEC[SENTER] and one of two things happens. > > 1. The system hangs during ACM execution and never re-enters tboot. > 2. ACM completes and successfully re-enters tboot in SMX mode. Shortly > after the system hangs while executing in tboot (seemingly at random > spots from a tboot perspective). > > Thanks > Ross > > > -----Original Message----- > From: Karthik . [mailto:tr...@gm...] > Sent: Monday, November 10, 2008 4:48 PM > To: Ross Philipson > Cc: Jonathan M. McCune; tbo...@li... > Subject: Re: [tboot-devel] Buying a machine that will actually work with > TXT > > Sure, I can help you in this. Can you please tell me the bios version > you are using? > > Thanks > Karthik > > On Mon, Nov 10, 2008 at 1:50 PM, Ross Philipson > <Ros...@ci...> wrote: >> Karthik, >> >> I also have an SINIT from Intel that is supposed to be the latest. My >> reply below was to indicate that I thought the HP laptops did not have > a >> valid ACM shipped in the BIOS region. Unfortunately even with the > SINIT >> module, I cannot get tboot working on these HPs. Did you do anything >> special to get it to work? >> >> Thanks >> Ross >> >> -----Original Message----- >> From: Karthik . [mailto:tr...@gm...] >> Sent: Monday, November 10, 2008 2:39 PM >> To: Ross Philipson >> Cc: Jonathan M. McCune; tbo...@li... >> Subject: Re: [tboot-devel] Buying a machine that will actually work > with >> TXT >> >> Hi Ross >> >> Tboot worked for me on the 6930p, probably because I have the correct >> latest SINIT module for the mobile platform. I am sure, once Intel >> makes this modules available for the public, you can try tboot without >> any issues. Thanks >> >> Karthik >> >> On Mon, Nov 10, 2008 at 12:43 PM, Ross Philipson >> <Ros...@ci...> wrote: >>> We have several HP 6930p laptops with MV chipset (GM45/ICH9). The >>> systems do not seem to ship with the AC module pre-loaded in BIOS > from >>> what I can tell. At least when I use tboot without an external SINIT >>> module, tboot fails to validate the contents of the ACM BIOS area. I >>> think Intel should be making the SINIT for this platforms available >>> soon. >>> >>> Thanks >>> Ross >>> >>> -----Original Message----- >>> From: Karthik . [mailto:tr...@gm...] >>> Sent: Monday, November 10, 2008 1:37 PM >>> To: Jonathan M. McCune >>> Cc: tbo...@li... >>> Subject: Re: [tboot-devel] Buying a machine that will actually work >> with >>> TXT >>> >>> Hi Jon, >>> >>> That is a good question. In fact I think Joe would be the right > person >>> to answer this. We (HP) get the latest BIOS and SINIT AC modules from >>> Intel for our mobile platforms. I am not sure if the SINIT modules >>> available on the Tboot sourceforge website (for desktop chipsets) can >>> be used on the mobile platforms which has the bios integrated with >>> latest BIOS AC module (I think both the modules should match for > tboot >>> to work). I am guessing that the SINIT modules for the mobile >>> platforms will also be soon uploaded onto the sourceforge website. >>> >>> Thanks >>> Karthik >>> >>> On Mon, Nov 10, 2008 at 12:18 PM, Jonathan M. McCune >> <jon...@cm...> >>> wrote: >>>> Hi Karthik, >>>> >>>> Thanks for the quick response. >>>> Intel, are there SINIT modules available for these systems? Are > they >>>> shipping with SINIT modules as part of the BIOS? >>>> >>>> Thanks, >>>> -Jon >>>> >>>> >>>> >>>> Karthik . wrote: >>>>> >>>>> Hi Jon >>>>> >>>>> As far as I know, the new 2008 Elitebook platforms from HP support >>>>> TXT/Tboot feature. >>>>> >>>>> >>>>> >>> >> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF25a/321957-321957-64295-374064 >>> 5-89315-3688868.html >>>>> >>>>> >>> >> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-374064 >>> 5-3329741-3782310.html >>>>> >>>>> >>> >> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-374064 >>> 5-3329741-3784202.html >>>>> >>>>> >>> >> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-374064 >>> 5-306995-3784558-3784561-3802771.html >>>>> >>>>> >>> >> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-374064 >>> 5-306995-3782222-3782253-3782268.html >>>>> >>>>> Thanks >>>>> Karthik >>>>> >>>>> >>>>> >>>>> On Mon, Nov 10, 2008 at 11:27 AM, Jonathan M. McCune >>> <jon...@cm...> >>>>> wrote: >>>>> >>>>>> >>>>>> Hi Karthik, tboot-devel, >>>>>> >>>>>> Any news on the HP BIOS? >>>>>> >>>>>> Are there any laptops available yet that support tboot? I seem to >>>>>> remember a >>>>>> post from Joe explaining when they might become available but I've >>> been >>>>>> unable to locate it. >>>>>> >>>>>> A search on newegg.com for laptops with vPro turns up several >>> machines. >>>>>> Lenovo and Toshiba seem to be using an M45 chipset. ASUS has one >>> with a >>>>>> GM965. My understanding is still that Q35 and X38 are the only > ones >>> that >>>>>> work today. >>>>>> >>>>>> Thanks! >>>>>> -Jon >>>>>> >>>>>> >>>>>> >>>>>> Karthik . wrote: >>>>>> >>>>>>> >>>>>>> HP Desktop Bios team is working on this issue and may release it >> in >>>>>>> couple >>>>>>> of weeks. Thanks >>>>>>> >>>>>>> Karthik >>>>>>> >>>>>>> >>>>>>> *Re: [tboot-devel] Buying a machine that will actually work with >>> TXT* >>>>>>> From: Jonathan M. McCune <jonmccune@cm...> - 2008-10-09 17:18 >>>>>>> fyi... >>>>>>> >>>>>>> It seems that the HP Compaq dc7800 does _not_ include a reset >>> button >>>>>>> either. >>>>>>> >>>>>>> -Jon >>>>>>> >>>>>>> >>>>>>> Jonathan M. McCune wrote: >>>>>>> >>>>>>>> >>>>>>>> Hal Finney wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> When Trusted Execution was announced, 3 models of computers > were >>>>>>>>> identified as supporting it: The HP Compaq dc7800, Dell > OptiPlex >>> 755 >>>>>>>>> PC, and the Lenovo ThinkCentre M57p. I don't know of any others >>> that >>>>>>>>> have been added to that list since then. >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> Does anybody know whether the HP or Lenovo systems include a >> reset >>>>>>>> button? At least the Ultra Slim Form Factor Optiplex 755s have > no >>> reset >>>>>>>> button, meaning that debugging a system hang requires a power >>> cycle >>>>>>>> that >>>>>>>> clears LT.ERRORCODE, making debugging substantially more >>> difficult. >>>>>>>> >>>>>>>> >>>>>>>> Alternatively, does anybody know another way to trigger a reset >> on >>> one >>>>>>>> of these systems? I'm told that there is a CMOS reset byte, and >>> that it >>>>>>>> may be possible to write a value to it that causes the "soft" >>> power >>>>>>>> button on the Optiplex to cause a reset instead of a power off. > I >>> have >>>>>>>> not investigated this yet, as I'd rather just get a different >>> machine. >>>>>>>> >>>>>>>> >>>>>>>> Thanks, >>>>>>>> -Jon >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>> >> > ------------------------------------------------------------------------ >>> - >>>>>>>> This SF.Net email is sponsored by the Moblin Your Move >> Developer's >>>>>>>> challenge >>>>>>>> Build the coolest Linux based applications with Moblin SDK & win >>> great >>>>>>>> prizes >>>>>>>> Grand prize is a trip for two to an Open Source event anywhere > in >>> the >>>>>>>> world >>>>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>>>>>> <http://moblin-contest.org/redirect.php?banner_id=100&url=/> >>>>>>>> _______________________________________________ >>>>>>>> tboot-devel mailing list >>>>>>>> tboot-devel@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/tboot-devel >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>> >> > ------------------------------------------------------------------------ >>>>>>> >>>>>>> >>>>>>> >>> >> > ------------------------------------------------------------------------ >>> - >>>>>>> This SF.Net email is sponsored by the Moblin Your Move > Developer's >>>>>>> challenge >>>>>>> Build the coolest Linux based applications with Moblin SDK & win >>> great >>>>>>> prizes >>>>>>> Grand prize is a trip for two to an Open Source event anywhere in >>> the >>>>>>> world >>>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>>>>> >>> >> > ------------------------------------------------------------------------ >>>>>>> >>>>>>> _______________________________________________ >>>>>>> tboot-devel mailing list >>>>>>> tbo...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/tboot-devel >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> > ------------------------------------------------------------------------ >>> - >>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>> challenge >>> Build the coolest Linux based applications with Moblin SDK & win > great >>> prizes >>> Grand prize is a trip for two to an Open Source event anywhere in the >>> world >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> _______________________________________________ >>> tboot-devel mailing list >>> tbo...@li... >>> https://lists.sourceforge.net/lists/listinfo/tboot-devel >>> >> > |
|
From: Lil E. <Lil...@gm...> - 2008-11-12 13:16:05
|
Hi, I was wondering whats the status and/or roadmap for late launch with tboot, as I was looking at getting some kind of late launch to work? I do believe some people on this mailing list are working on a late launch proof of concept? What's the status there? thanks lIl -- GMX Download-Spiele: Preizsturz! Alle Puzzle-Spiele Deluxe über 60% billiger. http://games.entertainment.gmx.net/de/entertainment/games/download/puzzle/index.html |
|
From: Ross P. <Ros...@ci...> - 2008-11-12 12:43:22
|
Great. I will update the early serial logging to be similar to xen including allowing you to specify the IO port and crystal frequency to support external serial port cards and send a patch. I think I sent you a patch earlier to enable early VGA but that was trivial - the VGA support is already there, just not used so it will need a command line way to turn it on. I would probably just use the xen command line format unless anyone has a better idea. Thanks Ross From: Cihula, Joseph [mailto:jos...@in...] Sent: Wednesday, November 12, 2008 4:27 AM To: Ross Philipson; tbo...@li... Subject: RE: Enhance serial support in tboot I've been giving some thought to this and I think that it would be valuable to have a command line parameter that allowed specifying how logging is done: VGA, memory, serial (and any combination of them or lack of them). The serial parameter would also need to support specifying the various serial configs . I've been holding off on this because I wanted to limit the amount of command line options since the command line is not currently part of the measurement of tboot, and thus there is a greater potential for malicious manipulation of the code via command line. E.g. if by adding more command line options one of them introduces a buffer overflow then there would be no way to determine if a given invocation of tboot was done with such a malicious command line. But I think that it is time to bite the bullet and add the command line to the tboot measurement. So with that support, making the command line more complex will be less risky. I'll take care of the command line measurement changes, but I would welcome patches for the above logging support. Joe P.S. Back from vacation now so emails should be more timely. From: Ross Philipson [mailto:Ros...@ci...] Sent: Monday, November 03, 2008 11:14 AM To: tbo...@li... Subject: [tboot-devel] Enhance serial support in tboot I have recently been working on laptops that do not have serial ports so I have been using an ExpressCard serial adapter. I had to make modification to tboot to use a different IO port and clock frequency. I have found that having serial debug output for tboot is incredibly valuable during development. The Xen console driver (on which the tboot early_printk is loosely based as it seems) allows serial console configuration with command line arguments (including setting the clock freq. now). I was thinking of pulling this into tboot but I wanted to see if the community thought this was something valuable to do - something that could be incorporated in tboot? Thanks Ross Ross Philipson Senior Software Engineer Citrix Systems, Inc 14 Crosby Drive Bedford, MA 01730 781-301-7949 ros...@ci... |
|
From: Cihula, J. <jos...@in...> - 2008-11-12 09:26:44
|
I've been giving some thought to this and I think that it would be valuable to have a command line parameter that allowed specifying how logging is done: VGA, memory, serial (and any combination of them or lack of them). The serial parameter would also need to support specifying the various serial configs . I've been holding off on this because I wanted to limit the amount of command line options since the command line is not currently part of the measurement of tboot, and thus there is a greater potential for malicious manipulation of the code via command line. E.g. if by adding more command line options one of them introduces a buffer overflow then there would be no way to determine if a given invocation of tboot was done with such a malicious command line. But I think that it is time to bite the bullet and add the command line to the tboot measurement. So with that support, making the command line more complex will be less risky. I'll take care of the command line measurement changes, but I would welcome patches for the above logging support. Joe P.S. Back from vacation now so emails should be more timely. From: Ross Philipson [mailto:Ros...@ci...] Sent: Monday, November 03, 2008 11:14 AM To: tbo...@li... Subject: [tboot-devel] Enhance serial support in tboot I have recently been working on laptops that do not have serial ports so I have been using an ExpressCard serial adapter. I had to make modification to tboot to use a different IO port and clock frequency. I have found that having serial debug output for tboot is incredibly valuable during development. The Xen console driver (on which the tboot early_printk is loosely based as it seems) allows serial console configuration with command line arguments (including setting the clock freq. now). I was thinking of pulling this into tboot but I wanted to see if the community thought this was something valuable to do - something that could be incorporated in tboot? Thanks Ross Ross Philipson Senior Software Engineer Citrix Systems, Inc 14 Crosby Drive Bedford, MA 01730 781-301-7949 ros...@ci...<mailto:ros...@ci...> |
|
From: Karthik . <tr...@gm...> - 2008-11-10 22:18:37
|
Sure, I can help you in this. Can you please tell me the bios version you are using? Thanks Karthik On Mon, Nov 10, 2008 at 1:50 PM, Ross Philipson <Ros...@ci...> wrote: > Karthik, > > I also have an SINIT from Intel that is supposed to be the latest. My > reply below was to indicate that I thought the HP laptops did not have a > valid ACM shipped in the BIOS region. Unfortunately even with the SINIT > module, I cannot get tboot working on these HPs. Did you do anything > special to get it to work? > > Thanks > Ross > > -----Original Message----- > From: Karthik . [mailto:tr...@gm...] > Sent: Monday, November 10, 2008 2:39 PM > To: Ross Philipson > Cc: Jonathan M. McCune; tbo...@li... > Subject: Re: [tboot-devel] Buying a machine that will actually work with > TXT > > Hi Ross > > Tboot worked for me on the 6930p, probably because I have the correct > latest SINIT module for the mobile platform. I am sure, once Intel > makes this modules available for the public, you can try tboot without > any issues. Thanks > > Karthik > > On Mon, Nov 10, 2008 at 12:43 PM, Ross Philipson > <Ros...@ci...> wrote: >> We have several HP 6930p laptops with MV chipset (GM45/ICH9). The >> systems do not seem to ship with the AC module pre-loaded in BIOS from >> what I can tell. At least when I use tboot without an external SINIT >> module, tboot fails to validate the contents of the ACM BIOS area. I >> think Intel should be making the SINIT for this platforms available >> soon. >> >> Thanks >> Ross >> >> -----Original Message----- >> From: Karthik . [mailto:tr...@gm...] >> Sent: Monday, November 10, 2008 1:37 PM >> To: Jonathan M. McCune >> Cc: tbo...@li... >> Subject: Re: [tboot-devel] Buying a machine that will actually work > with >> TXT >> >> Hi Jon, >> >> That is a good question. In fact I think Joe would be the right person >> to answer this. We (HP) get the latest BIOS and SINIT AC modules from >> Intel for our mobile platforms. I am not sure if the SINIT modules >> available on the Tboot sourceforge website (for desktop chipsets) can >> be used on the mobile platforms which has the bios integrated with >> latest BIOS AC module (I think both the modules should match for tboot >> to work). I am guessing that the SINIT modules for the mobile >> platforms will also be soon uploaded onto the sourceforge website. >> >> Thanks >> Karthik >> >> On Mon, Nov 10, 2008 at 12:18 PM, Jonathan M. McCune > <jon...@cm...> >> wrote: >>> Hi Karthik, >>> >>> Thanks for the quick response. >>> Intel, are there SINIT modules available for these systems? Are they >>> shipping with SINIT modules as part of the BIOS? >>> >>> Thanks, >>> -Jon >>> >>> >>> >>> Karthik . wrote: >>>> >>>> Hi Jon >>>> >>>> As far as I know, the new 2008 Elitebook platforms from HP support >>>> TXT/Tboot feature. >>>> >>>> >>>> >> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF25a/321957-321957-64295-374064 >> 5-89315-3688868.html >>>> >>>> >> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-374064 >> 5-3329741-3782310.html >>>> >>>> >> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-374064 >> 5-3329741-3784202.html >>>> >>>> >> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-374064 >> 5-306995-3784558-3784561-3802771.html >>>> >>>> >> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-374064 >> 5-306995-3782222-3782253-3782268.html >>>> >>>> Thanks >>>> Karthik >>>> >>>> >>>> >>>> On Mon, Nov 10, 2008 at 11:27 AM, Jonathan M. McCune >> <jon...@cm...> >>>> wrote: >>>> >>>>> >>>>> Hi Karthik, tboot-devel, >>>>> >>>>> Any news on the HP BIOS? >>>>> >>>>> Are there any laptops available yet that support tboot? I seem to >>>>> remember a >>>>> post from Joe explaining when they might become available but I've >> been >>>>> unable to locate it. >>>>> >>>>> A search on newegg.com for laptops with vPro turns up several >> machines. >>>>> Lenovo and Toshiba seem to be using an M45 chipset. ASUS has one >> with a >>>>> GM965. My understanding is still that Q35 and X38 are the only ones >> that >>>>> work today. >>>>> >>>>> Thanks! >>>>> -Jon >>>>> >>>>> >>>>> >>>>> Karthik . wrote: >>>>> >>>>>> >>>>>> HP Desktop Bios team is working on this issue and may release it > in >>>>>> couple >>>>>> of weeks. Thanks >>>>>> >>>>>> Karthik >>>>>> >>>>>> >>>>>> *Re: [tboot-devel] Buying a machine that will actually work with >> TXT* >>>>>> From: Jonathan M. McCune <jonmccune@cm...> - 2008-10-09 17:18 >>>>>> fyi... >>>>>> >>>>>> It seems that the HP Compaq dc7800 does _not_ include a reset >> button >>>>>> either. >>>>>> >>>>>> -Jon >>>>>> >>>>>> >>>>>> Jonathan M. McCune wrote: >>>>>> >>>>>>> >>>>>>> Hal Finney wrote: >>>>>>> >>>>>>>> >>>>>>>> When Trusted Execution was announced, 3 models of computers were >>>>>>>> identified as supporting it: The HP Compaq dc7800, Dell OptiPlex >> 755 >>>>>>>> PC, and the Lenovo ThinkCentre M57p. I don't know of any others >> that >>>>>>>> have been added to that list since then. >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> Does anybody know whether the HP or Lenovo systems include a > reset >>>>>>> button? At least the Ultra Slim Form Factor Optiplex 755s have no >> reset >>>>>>> button, meaning that debugging a system hang requires a power >> cycle >>>>>>> that >>>>>>> clears LT.ERRORCODE, making debugging substantially more >> difficult. >>>>>>> >>>>>>> >>>>>>> Alternatively, does anybody know another way to trigger a reset > on >> one >>>>>>> of these systems? I'm told that there is a CMOS reset byte, and >> that it >>>>>>> may be possible to write a value to it that causes the "soft" >> power >>>>>>> button on the Optiplex to cause a reset instead of a power off. I >> have >>>>>>> not investigated this yet, as I'd rather just get a different >> machine. >>>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> -Jon >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >> > ------------------------------------------------------------------------ >> - >>>>>>> This SF.Net email is sponsored by the Moblin Your Move > Developer's >>>>>>> challenge >>>>>>> Build the coolest Linux based applications with Moblin SDK & win >> great >>>>>>> prizes >>>>>>> Grand prize is a trip for two to an Open Source event anywhere in >> the >>>>>>> world >>>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>>>>> <http://moblin-contest.org/redirect.php?banner_id=100&url=/> >>>>>>> _______________________________________________ >>>>>>> tboot-devel mailing list >>>>>>> tboot-devel@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/tboot-devel >>>>>>> >>>>>>> >>>>>> >>>>>> >> > ------------------------------------------------------------------------ >>>>>> >>>>>> >>>>>> >> > ------------------------------------------------------------------------ >> - >>>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>>>> challenge >>>>>> Build the coolest Linux based applications with Moblin SDK & win >> great >>>>>> prizes >>>>>> Grand prize is a trip for two to an Open Source event anywhere in >> the >>>>>> world >>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>>>> >> > ------------------------------------------------------------------------ >>>>>> >>>>>> _______________________________________________ >>>>>> tboot-devel mailing list >>>>>> tbo...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/tboot-devel >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > ------------------------------------------------------------------------ >> - >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> tboot-devel mailing list >> tbo...@li... >> https://lists.sourceforge.net/lists/listinfo/tboot-devel >> > |
|
From: Ross P. <Ros...@ci...> - 2008-11-10 22:02:10
|
I am using F.0B - the latest publically available for those systems. Tboot executes GETSEC[SENTER] and one of two things happens. 1. The system hangs during ACM execution and never re-enters tboot. 2. ACM completes and successfully re-enters tboot in SMX mode. Shortly after the system hangs while executing in tboot (seemingly at random spots from a tboot perspective). Thanks Ross -----Original Message----- From: Karthik . [mailto:tr...@gm...] Sent: Monday, November 10, 2008 4:48 PM To: Ross Philipson Cc: Jonathan M. McCune; tbo...@li... Subject: Re: [tboot-devel] Buying a machine that will actually work with TXT Sure, I can help you in this. Can you please tell me the bios version you are using? Thanks Karthik On Mon, Nov 10, 2008 at 1:50 PM, Ross Philipson <Ros...@ci...> wrote: > Karthik, > > I also have an SINIT from Intel that is supposed to be the latest. My > reply below was to indicate that I thought the HP laptops did not have a > valid ACM shipped in the BIOS region. Unfortunately even with the SINIT > module, I cannot get tboot working on these HPs. Did you do anything > special to get it to work? > > Thanks > Ross > > -----Original Message----- > From: Karthik . [mailto:tr...@gm...] > Sent: Monday, November 10, 2008 2:39 PM > To: Ross Philipson > Cc: Jonathan M. McCune; tbo...@li... > Subject: Re: [tboot-devel] Buying a machine that will actually work with > TXT > > Hi Ross > > Tboot worked for me on the 6930p, probably because I have the correct > latest SINIT module for the mobile platform. I am sure, once Intel > makes this modules available for the public, you can try tboot without > any issues. Thanks > > Karthik > > On Mon, Nov 10, 2008 at 12:43 PM, Ross Philipson > <Ros...@ci...> wrote: >> We have several HP 6930p laptops with MV chipset (GM45/ICH9). The >> systems do not seem to ship with the AC module pre-loaded in BIOS from >> what I can tell. At least when I use tboot without an external SINIT >> module, tboot fails to validate the contents of the ACM BIOS area. I >> think Intel should be making the SINIT for this platforms available >> soon. >> >> Thanks >> Ross >> >> -----Original Message----- >> From: Karthik . [mailto:tr...@gm...] >> Sent: Monday, November 10, 2008 1:37 PM >> To: Jonathan M. McCune >> Cc: tbo...@li... >> Subject: Re: [tboot-devel] Buying a machine that will actually work > with >> TXT >> >> Hi Jon, >> >> That is a good question. In fact I think Joe would be the right person >> to answer this. We (HP) get the latest BIOS and SINIT AC modules from >> Intel for our mobile platforms. I am not sure if the SINIT modules >> available on the Tboot sourceforge website (for desktop chipsets) can >> be used on the mobile platforms which has the bios integrated with >> latest BIOS AC module (I think both the modules should match for tboot >> to work). I am guessing that the SINIT modules for the mobile >> platforms will also be soon uploaded onto the sourceforge website. >> >> Thanks >> Karthik >> >> On Mon, Nov 10, 2008 at 12:18 PM, Jonathan M. McCune > <jon...@cm...> >> wrote: >>> Hi Karthik, >>> >>> Thanks for the quick response. >>> Intel, are there SINIT modules available for these systems? Are they >>> shipping with SINIT modules as part of the BIOS? >>> >>> Thanks, >>> -Jon >>> >>> >>> >>> Karthik . wrote: >>>> >>>> Hi Jon >>>> >>>> As far as I know, the new 2008 Elitebook platforms from HP support >>>> TXT/Tboot feature. >>>> >>>> >>>> >> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF25a/321957-321957-64295-374064 >> 5-89315-3688868.html >>>> >>>> >> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-374064 >> 5-3329741-3782310.html >>>> >>>> >> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-374064 >> 5-3329741-3784202.html >>>> >>>> >> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-374064 >> 5-306995-3784558-3784561-3802771.html >>>> >>>> >> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-374064 >> 5-306995-3782222-3782253-3782268.html >>>> >>>> Thanks >>>> Karthik >>>> >>>> >>>> >>>> On Mon, Nov 10, 2008 at 11:27 AM, Jonathan M. McCune >> <jon...@cm...> >>>> wrote: >>>> >>>>> >>>>> Hi Karthik, tboot-devel, >>>>> >>>>> Any news on the HP BIOS? >>>>> >>>>> Are there any laptops available yet that support tboot? I seem to >>>>> remember a >>>>> post from Joe explaining when they might become available but I've >> been >>>>> unable to locate it. >>>>> >>>>> A search on newegg.com for laptops with vPro turns up several >> machines. >>>>> Lenovo and Toshiba seem to be using an M45 chipset. ASUS has one >> with a >>>>> GM965. My understanding is still that Q35 and X38 are the only ones >> that >>>>> work today. >>>>> >>>>> Thanks! >>>>> -Jon >>>>> >>>>> >>>>> >>>>> Karthik . wrote: >>>>> >>>>>> >>>>>> HP Desktop Bios team is working on this issue and may release it > in >>>>>> couple >>>>>> of weeks. Thanks >>>>>> >>>>>> Karthik >>>>>> >>>>>> >>>>>> *Re: [tboot-devel] Buying a machine that will actually work with >> TXT* >>>>>> From: Jonathan M. McCune <jonmccune@cm...> - 2008-10-09 17:18 >>>>>> fyi... >>>>>> >>>>>> It seems that the HP Compaq dc7800 does _not_ include a reset >> button >>>>>> either. >>>>>> >>>>>> -Jon >>>>>> >>>>>> >>>>>> Jonathan M. McCune wrote: >>>>>> >>>>>>> >>>>>>> Hal Finney wrote: >>>>>>> >>>>>>>> >>>>>>>> When Trusted Execution was announced, 3 models of computers were >>>>>>>> identified as supporting it: The HP Compaq dc7800, Dell OptiPlex >> 755 >>>>>>>> PC, and the Lenovo ThinkCentre M57p. I don't know of any others >> that >>>>>>>> have been added to that list since then. >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> Does anybody know whether the HP or Lenovo systems include a > reset >>>>>>> button? At least the Ultra Slim Form Factor Optiplex 755s have no >> reset >>>>>>> button, meaning that debugging a system hang requires a power >> cycle >>>>>>> that >>>>>>> clears LT.ERRORCODE, making debugging substantially more >> difficult. >>>>>>> >>>>>>> >>>>>>> Alternatively, does anybody know another way to trigger a reset > on >> one >>>>>>> of these systems? I'm told that there is a CMOS reset byte, and >> that it >>>>>>> may be possible to write a value to it that causes the "soft" >> power >>>>>>> button on the Optiplex to cause a reset instead of a power off. I >> have >>>>>>> not investigated this yet, as I'd rather just get a different >> machine. >>>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> -Jon >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >> > ------------------------------------------------------------------------ >> - >>>>>>> This SF.Net email is sponsored by the Moblin Your Move > Developer's >>>>>>> challenge >>>>>>> Build the coolest Linux based applications with Moblin SDK & win >> great >>>>>>> prizes >>>>>>> Grand prize is a trip for two to an Open Source event anywhere in >> the >>>>>>> world >>>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>>>>> <http://moblin-contest.org/redirect.php?banner_id=100&url=/> >>>>>>> _______________________________________________ >>>>>>> tboot-devel mailing list >>>>>>> tboot-devel@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/tboot-devel >>>>>>> >>>>>>> >>>>>> >>>>>> >> > ------------------------------------------------------------------------ >>>>>> >>>>>> >>>>>> >> > ------------------------------------------------------------------------ >> - >>>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>>>> challenge >>>>>> Build the coolest Linux based applications with Moblin SDK & win >> great >>>>>> prizes >>>>>> Grand prize is a trip for two to an Open Source event anywhere in >> the >>>>>> world >>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>>>> >> > ------------------------------------------------------------------------ >>>>>> >>>>>> _______________________________________________ >>>>>> tboot-devel mailing list >>>>>> tbo...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/tboot-devel >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > ------------------------------------------------------------------------ >> - >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> tboot-devel mailing list >> tbo...@li... >> https://lists.sourceforge.net/lists/listinfo/tboot-devel >> > |
|
From: Ross P. <Ros...@ci...> - 2008-11-10 19:50:05
|
Karthik, I also have an SINIT from Intel that is supposed to be the latest. My reply below was to indicate that I thought the HP laptops did not have a valid ACM shipped in the BIOS region. Unfortunately even with the SINIT module, I cannot get tboot working on these HPs. Did you do anything special to get it to work? Thanks Ross -----Original Message----- From: Karthik . [mailto:tr...@gm...] Sent: Monday, November 10, 2008 2:39 PM To: Ross Philipson Cc: Jonathan M. McCune; tbo...@li... Subject: Re: [tboot-devel] Buying a machine that will actually work with TXT Hi Ross Tboot worked for me on the 6930p, probably because I have the correct latest SINIT module for the mobile platform. I am sure, once Intel makes this modules available for the public, you can try tboot without any issues. Thanks Karthik On Mon, Nov 10, 2008 at 12:43 PM, Ross Philipson <Ros...@ci...> wrote: > We have several HP 6930p laptops with MV chipset (GM45/ICH9). The > systems do not seem to ship with the AC module pre-loaded in BIOS from > what I can tell. At least when I use tboot without an external SINIT > module, tboot fails to validate the contents of the ACM BIOS area. I > think Intel should be making the SINIT for this platforms available > soon. > > Thanks > Ross > > -----Original Message----- > From: Karthik . [mailto:tr...@gm...] > Sent: Monday, November 10, 2008 1:37 PM > To: Jonathan M. McCune > Cc: tbo...@li... > Subject: Re: [tboot-devel] Buying a machine that will actually work with > TXT > > Hi Jon, > > That is a good question. In fact I think Joe would be the right person > to answer this. We (HP) get the latest BIOS and SINIT AC modules from > Intel for our mobile platforms. I am not sure if the SINIT modules > available on the Tboot sourceforge website (for desktop chipsets) can > be used on the mobile platforms which has the bios integrated with > latest BIOS AC module (I think both the modules should match for tboot > to work). I am guessing that the SINIT modules for the mobile > platforms will also be soon uploaded onto the sourceforge website. > > Thanks > Karthik > > On Mon, Nov 10, 2008 at 12:18 PM, Jonathan M. McCune <jon...@cm...> > wrote: >> Hi Karthik, >> >> Thanks for the quick response. >> Intel, are there SINIT modules available for these systems? Are they >> shipping with SINIT modules as part of the BIOS? >> >> Thanks, >> -Jon >> >> >> >> Karthik . wrote: >>> >>> Hi Jon >>> >>> As far as I know, the new 2008 Elitebook platforms from HP support >>> TXT/Tboot feature. >>> >>> >>> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF25a/321957-321957-64295-374064 > 5-89315-3688868.html >>> >>> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-374064 > 5-3329741-3782310.html >>> >>> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-374064 > 5-3329741-3784202.html >>> >>> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-374064 > 5-306995-3784558-3784561-3802771.html >>> >>> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-374064 > 5-306995-3782222-3782253-3782268.html >>> >>> Thanks >>> Karthik >>> >>> >>> >>> On Mon, Nov 10, 2008 at 11:27 AM, Jonathan M. McCune > <jon...@cm...> >>> wrote: >>> >>>> >>>> Hi Karthik, tboot-devel, >>>> >>>> Any news on the HP BIOS? >>>> >>>> Are there any laptops available yet that support tboot? I seem to >>>> remember a >>>> post from Joe explaining when they might become available but I've > been >>>> unable to locate it. >>>> >>>> A search on newegg.com for laptops with vPro turns up several > machines. >>>> Lenovo and Toshiba seem to be using an M45 chipset. ASUS has one > with a >>>> GM965. My understanding is still that Q35 and X38 are the only ones > that >>>> work today. >>>> >>>> Thanks! >>>> -Jon >>>> >>>> >>>> >>>> Karthik . wrote: >>>> >>>>> >>>>> HP Desktop Bios team is working on this issue and may release it in >>>>> couple >>>>> of weeks. Thanks >>>>> >>>>> Karthik >>>>> >>>>> >>>>> *Re: [tboot-devel] Buying a machine that will actually work with > TXT* >>>>> From: Jonathan M. McCune <jonmccune@cm...> - 2008-10-09 17:18 >>>>> fyi... >>>>> >>>>> It seems that the HP Compaq dc7800 does _not_ include a reset > button >>>>> either. >>>>> >>>>> -Jon >>>>> >>>>> >>>>> Jonathan M. McCune wrote: >>>>> >>>>>> >>>>>> Hal Finney wrote: >>>>>> >>>>>>> >>>>>>> When Trusted Execution was announced, 3 models of computers were >>>>>>> identified as supporting it: The HP Compaq dc7800, Dell OptiPlex > 755 >>>>>>> PC, and the Lenovo ThinkCentre M57p. I don't know of any others > that >>>>>>> have been added to that list since then. >>>>>>> >>>>>>> >>>>>> >>>>>> Does anybody know whether the HP or Lenovo systems include a reset >>>>>> button? At least the Ultra Slim Form Factor Optiplex 755s have no > reset >>>>>> button, meaning that debugging a system hang requires a power > cycle >>>>>> that >>>>>> clears LT.ERRORCODE, making debugging substantially more > difficult. >>>>>> >>>>>> >>>>>> Alternatively, does anybody know another way to trigger a reset on > one >>>>>> of these systems? I'm told that there is a CMOS reset byte, and > that it >>>>>> may be possible to write a value to it that causes the "soft" > power >>>>>> button on the Optiplex to cause a reset instead of a power off. I > have >>>>>> not investigated this yet, as I'd rather just get a different > machine. >>>>>> >>>>>> >>>>>> Thanks, >>>>>> -Jon >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> > ------------------------------------------------------------------------ > - >>>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>>>> challenge >>>>>> Build the coolest Linux based applications with Moblin SDK & win > great >>>>>> prizes >>>>>> Grand prize is a trip for two to an Open Source event anywhere in > the >>>>>> world >>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>>>> <http://moblin-contest.org/redirect.php?banner_id=100&url=/> >>>>>> _______________________________________________ >>>>>> tboot-devel mailing list >>>>>> tboot-devel@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/tboot-devel >>>>>> >>>>>> >>>>> >>>>> > ------------------------------------------------------------------------ >>>>> >>>>> >>>>> > ------------------------------------------------------------------------ > - >>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>>> challenge >>>>> Build the coolest Linux based applications with Moblin SDK & win > great >>>>> prizes >>>>> Grand prize is a trip for two to an Open Source event anywhere in > the >>>>> world >>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>>> > ------------------------------------------------------------------------ >>>>> >>>>> _______________________________________________ >>>>> tboot-devel mailing list >>>>> tbo...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/tboot-devel >>>>> >>>>> >>>> >>>> >>> >>> >> >> > > ------------------------------------------------------------------------ > - > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > tboot-devel mailing list > tbo...@li... > https://lists.sourceforge.net/lists/listinfo/tboot-devel > |
|
From: Karthik . <tr...@gm...> - 2008-11-10 19:39:29
|
Hi Ross Tboot worked for me on the 6930p, probably because I have the correct latest SINIT module for the mobile platform. I am sure, once Intel makes this modules available for the public, you can try tboot without any issues. Thanks Karthik On Mon, Nov 10, 2008 at 12:43 PM, Ross Philipson <Ros...@ci...> wrote: > We have several HP 6930p laptops with MV chipset (GM45/ICH9). The > systems do not seem to ship with the AC module pre-loaded in BIOS from > what I can tell. At least when I use tboot without an external SINIT > module, tboot fails to validate the contents of the ACM BIOS area. I > think Intel should be making the SINIT for this platforms available > soon. > > Thanks > Ross > > -----Original Message----- > From: Karthik . [mailto:tr...@gm...] > Sent: Monday, November 10, 2008 1:37 PM > To: Jonathan M. McCune > Cc: tbo...@li... > Subject: Re: [tboot-devel] Buying a machine that will actually work with > TXT > > Hi Jon, > > That is a good question. In fact I think Joe would be the right person > to answer this. We (HP) get the latest BIOS and SINIT AC modules from > Intel for our mobile platforms. I am not sure if the SINIT modules > available on the Tboot sourceforge website (for desktop chipsets) can > be used on the mobile platforms which has the bios integrated with > latest BIOS AC module (I think both the modules should match for tboot > to work). I am guessing that the SINIT modules for the mobile > platforms will also be soon uploaded onto the sourceforge website. > > Thanks > Karthik > > On Mon, Nov 10, 2008 at 12:18 PM, Jonathan M. McCune <jon...@cm...> > wrote: >> Hi Karthik, >> >> Thanks for the quick response. >> Intel, are there SINIT modules available for these systems? Are they >> shipping with SINIT modules as part of the BIOS? >> >> Thanks, >> -Jon >> >> >> >> Karthik . wrote: >>> >>> Hi Jon >>> >>> As far as I know, the new 2008 Elitebook platforms from HP support >>> TXT/Tboot feature. >>> >>> >>> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF25a/321957-321957-64295-374064 > 5-89315-3688868.html >>> >>> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-374064 > 5-3329741-3782310.html >>> >>> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-374064 > 5-3329741-3784202.html >>> >>> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-374064 > 5-306995-3784558-3784561-3802771.html >>> >>> > http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-374064 > 5-306995-3782222-3782253-3782268.html >>> >>> Thanks >>> Karthik >>> >>> >>> >>> On Mon, Nov 10, 2008 at 11:27 AM, Jonathan M. McCune > <jon...@cm...> >>> wrote: >>> >>>> >>>> Hi Karthik, tboot-devel, >>>> >>>> Any news on the HP BIOS? >>>> >>>> Are there any laptops available yet that support tboot? I seem to >>>> remember a >>>> post from Joe explaining when they might become available but I've > been >>>> unable to locate it. >>>> >>>> A search on newegg.com for laptops with vPro turns up several > machines. >>>> Lenovo and Toshiba seem to be using an M45 chipset. ASUS has one > with a >>>> GM965. My understanding is still that Q35 and X38 are the only ones > that >>>> work today. >>>> >>>> Thanks! >>>> -Jon >>>> >>>> >>>> >>>> Karthik . wrote: >>>> >>>>> >>>>> HP Desktop Bios team is working on this issue and may release it in >>>>> couple >>>>> of weeks. Thanks >>>>> >>>>> Karthik >>>>> >>>>> >>>>> *Re: [tboot-devel] Buying a machine that will actually work with > TXT* >>>>> From: Jonathan M. McCune <jonmccune@cm...> - 2008-10-09 17:18 >>>>> fyi... >>>>> >>>>> It seems that the HP Compaq dc7800 does _not_ include a reset > button >>>>> either. >>>>> >>>>> -Jon >>>>> >>>>> >>>>> Jonathan M. McCune wrote: >>>>> >>>>>> >>>>>> Hal Finney wrote: >>>>>> >>>>>>> >>>>>>> When Trusted Execution was announced, 3 models of computers were >>>>>>> identified as supporting it: The HP Compaq dc7800, Dell OptiPlex > 755 >>>>>>> PC, and the Lenovo ThinkCentre M57p. I don't know of any others > that >>>>>>> have been added to that list since then. >>>>>>> >>>>>>> >>>>>> >>>>>> Does anybody know whether the HP or Lenovo systems include a reset >>>>>> button? At least the Ultra Slim Form Factor Optiplex 755s have no > reset >>>>>> button, meaning that debugging a system hang requires a power > cycle >>>>>> that >>>>>> clears LT.ERRORCODE, making debugging substantially more > difficult. >>>>>> >>>>>> >>>>>> Alternatively, does anybody know another way to trigger a reset on > one >>>>>> of these systems? I'm told that there is a CMOS reset byte, and > that it >>>>>> may be possible to write a value to it that causes the "soft" > power >>>>>> button on the Optiplex to cause a reset instead of a power off. I > have >>>>>> not investigated this yet, as I'd rather just get a different > machine. >>>>>> >>>>>> >>>>>> Thanks, >>>>>> -Jon >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> > ------------------------------------------------------------------------ > - >>>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>>>> challenge >>>>>> Build the coolest Linux based applications with Moblin SDK & win > great >>>>>> prizes >>>>>> Grand prize is a trip for two to an Open Source event anywhere in > the >>>>>> world >>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>>>> <http://moblin-contest.org/redirect.php?banner_id=100&url=/> >>>>>> _______________________________________________ >>>>>> tboot-devel mailing list >>>>>> tboot-devel@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/tboot-devel >>>>>> >>>>>> >>>>> >>>>> > ------------------------------------------------------------------------ >>>>> >>>>> >>>>> > ------------------------------------------------------------------------ > - >>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>>> challenge >>>>> Build the coolest Linux based applications with Moblin SDK & win > great >>>>> prizes >>>>> Grand prize is a trip for two to an Open Source event anywhere in > the >>>>> world >>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>>> > ------------------------------------------------------------------------ >>>>> >>>>> _______________________________________________ >>>>> tboot-devel mailing list >>>>> tbo...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/tboot-devel >>>>> >>>>> >>>> >>>> >>> >>> >> >> > > ------------------------------------------------------------------------ > - > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > tboot-devel mailing list > tbo...@li... > https://lists.sourceforge.net/lists/listinfo/tboot-devel > |
|
From: Ross P. <Ros...@ci...> - 2008-11-10 18:43:36
|
We have several HP 6930p laptops with MV chipset (GM45/ICH9). The systems do not seem to ship with the AC module pre-loaded in BIOS from what I can tell. At least when I use tboot without an external SINIT module, tboot fails to validate the contents of the ACM BIOS area. I think Intel should be making the SINIT for this platforms available soon. Thanks Ross -----Original Message----- From: Karthik . [mailto:tr...@gm...] Sent: Monday, November 10, 2008 1:37 PM To: Jonathan M. McCune Cc: tbo...@li... Subject: Re: [tboot-devel] Buying a machine that will actually work with TXT Hi Jon, That is a good question. In fact I think Joe would be the right person to answer this. We (HP) get the latest BIOS and SINIT AC modules from Intel for our mobile platforms. I am not sure if the SINIT modules available on the Tboot sourceforge website (for desktop chipsets) can be used on the mobile platforms which has the bios integrated with latest BIOS AC module (I think both the modules should match for tboot to work). I am guessing that the SINIT modules for the mobile platforms will also be soon uploaded onto the sourceforge website. Thanks Karthik On Mon, Nov 10, 2008 at 12:18 PM, Jonathan M. McCune <jon...@cm...> wrote: > Hi Karthik, > > Thanks for the quick response. > Intel, are there SINIT modules available for these systems? Are they > shipping with SINIT modules as part of the BIOS? > > Thanks, > -Jon > > > > Karthik . wrote: >> >> Hi Jon >> >> As far as I know, the new 2008 Elitebook platforms from HP support >> TXT/Tboot feature. >> >> >> http://h10010.www1.hp.com/wwpc/us/en/sm/WF25a/321957-321957-64295-374064 5-89315-3688868.html >> >> http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-374064 5-3329741-3782310.html >> >> http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-374064 5-3329741-3784202.html >> >> http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-374064 5-306995-3784558-3784561-3802771.html >> >> http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-374064 5-306995-3782222-3782253-3782268.html >> >> Thanks >> Karthik >> >> >> >> On Mon, Nov 10, 2008 at 11:27 AM, Jonathan M. McCune <jon...@cm...> >> wrote: >> >>> >>> Hi Karthik, tboot-devel, >>> >>> Any news on the HP BIOS? >>> >>> Are there any laptops available yet that support tboot? I seem to >>> remember a >>> post from Joe explaining when they might become available but I've been >>> unable to locate it. >>> >>> A search on newegg.com for laptops with vPro turns up several machines. >>> Lenovo and Toshiba seem to be using an M45 chipset. ASUS has one with a >>> GM965. My understanding is still that Q35 and X38 are the only ones that >>> work today. >>> >>> Thanks! >>> -Jon >>> >>> >>> >>> Karthik . wrote: >>> >>>> >>>> HP Desktop Bios team is working on this issue and may release it in >>>> couple >>>> of weeks. Thanks >>>> >>>> Karthik >>>> >>>> >>>> *Re: [tboot-devel] Buying a machine that will actually work with TXT* >>>> From: Jonathan M. McCune <jonmccune@cm...> - 2008-10-09 17:18 >>>> fyi... >>>> >>>> It seems that the HP Compaq dc7800 does _not_ include a reset button >>>> either. >>>> >>>> -Jon >>>> >>>> >>>> Jonathan M. McCune wrote: >>>> >>>>> >>>>> Hal Finney wrote: >>>>> >>>>>> >>>>>> When Trusted Execution was announced, 3 models of computers were >>>>>> identified as supporting it: The HP Compaq dc7800, Dell OptiPlex 755 >>>>>> PC, and the Lenovo ThinkCentre M57p. I don't know of any others that >>>>>> have been added to that list since then. >>>>>> >>>>>> >>>>> >>>>> Does anybody know whether the HP or Lenovo systems include a reset >>>>> button? At least the Ultra Slim Form Factor Optiplex 755s have no reset >>>>> button, meaning that debugging a system hang requires a power cycle >>>>> that >>>>> clears LT.ERRORCODE, making debugging substantially more difficult. >>>>> >>>>> >>>>> Alternatively, does anybody know another way to trigger a reset on one >>>>> of these systems? I'm told that there is a CMOS reset byte, and that it >>>>> may be possible to write a value to it that causes the "soft" power >>>>> button on the Optiplex to cause a reset instead of a power off. I have >>>>> not investigated this yet, as I'd rather just get a different machine. >>>>> >>>>> >>>>> Thanks, >>>>> -Jon >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------ - >>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>>> challenge >>>>> Build the coolest Linux based applications with Moblin SDK & win great >>>>> prizes >>>>> Grand prize is a trip for two to an Open Source event anywhere in the >>>>> world >>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>>> <http://moblin-contest.org/redirect.php?banner_id=100&url=/> >>>>> _______________________________________________ >>>>> tboot-devel mailing list >>>>> tboot-devel@li... >>>>> https://lists.sourceforge.net/lists/listinfo/tboot-devel >>>>> >>>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> ------------------------------------------------------------------------ - >>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>> challenge >>>> Build the coolest Linux based applications with Moblin SDK & win great >>>> prizes >>>> Grand prize is a trip for two to an Open Source event anywhere in the >>>> world >>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>> ------------------------------------------------------------------------ >>>> >>>> _______________________________________________ >>>> tboot-devel mailing list >>>> tbo...@li... >>>> https://lists.sourceforge.net/lists/listinfo/tboot-devel >>>> >>>> >>> >>> >> >> > > ------------------------------------------------------------------------ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ tboot-devel mailing list tbo...@li... https://lists.sourceforge.net/lists/listinfo/tboot-devel |
|
From: Karthik . <tr...@gm...> - 2008-11-10 18:37:26
|
Hi Jon, That is a good question. In fact I think Joe would be the right person to answer this. We (HP) get the latest BIOS and SINIT AC modules from Intel for our mobile platforms. I am not sure if the SINIT modules available on the Tboot sourceforge website (for desktop chipsets) can be used on the mobile platforms which has the bios integrated with latest BIOS AC module (I think both the modules should match for tboot to work). I am guessing that the SINIT modules for the mobile platforms will also be soon uploaded onto the sourceforge website. Thanks Karthik On Mon, Nov 10, 2008 at 12:18 PM, Jonathan M. McCune <jon...@cm...> wrote: > Hi Karthik, > > Thanks for the quick response. > Intel, are there SINIT modules available for these systems? Are they > shipping with SINIT modules as part of the BIOS? > > Thanks, > -Jon > > > > Karthik . wrote: >> >> Hi Jon >> >> As far as I know, the new 2008 Elitebook platforms from HP support >> TXT/Tboot feature. >> >> >> http://h10010.www1.hp.com/wwpc/us/en/sm/WF25a/321957-321957-64295-3740645-89315-3688868.html >> >> http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-3740645-3329741-3782310.html >> >> http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-3740645-3329741-3784202.html >> >> http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-3740645-306995-3784558-3784561-3802771.html >> >> http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-3740645-306995-3782222-3782253-3782268.html >> >> Thanks >> Karthik >> >> >> >> On Mon, Nov 10, 2008 at 11:27 AM, Jonathan M. McCune <jon...@cm...> >> wrote: >> >>> >>> Hi Karthik, tboot-devel, >>> >>> Any news on the HP BIOS? >>> >>> Are there any laptops available yet that support tboot? I seem to >>> remember a >>> post from Joe explaining when they might become available but I've been >>> unable to locate it. >>> >>> A search on newegg.com for laptops with vPro turns up several machines. >>> Lenovo and Toshiba seem to be using an M45 chipset. ASUS has one with a >>> GM965. My understanding is still that Q35 and X38 are the only ones that >>> work today. >>> >>> Thanks! >>> -Jon >>> >>> >>> >>> Karthik . wrote: >>> >>>> >>>> HP Desktop Bios team is working on this issue and may release it in >>>> couple >>>> of weeks. Thanks >>>> >>>> Karthik >>>> >>>> >>>> *Re: [tboot-devel] Buying a machine that will actually work with TXT* >>>> From: Jonathan M. McCune <jonmccune@cm...> - 2008-10-09 17:18 >>>> fyi... >>>> >>>> It seems that the HP Compaq dc7800 does _not_ include a reset button >>>> either. >>>> >>>> -Jon >>>> >>>> >>>> Jonathan M. McCune wrote: >>>> >>>>> >>>>> Hal Finney wrote: >>>>> >>>>>> >>>>>> When Trusted Execution was announced, 3 models of computers were >>>>>> identified as supporting it: The HP Compaq dc7800, Dell OptiPlex 755 >>>>>> PC, and the Lenovo ThinkCentre M57p. I don't know of any others that >>>>>> have been added to that list since then. >>>>>> >>>>>> >>>>> >>>>> Does anybody know whether the HP or Lenovo systems include a reset >>>>> button? At least the Ultra Slim Form Factor Optiplex 755s have no reset >>>>> button, meaning that debugging a system hang requires a power cycle >>>>> that >>>>> clears LT.ERRORCODE, making debugging substantially more difficult. >>>>> >>>>> >>>>> Alternatively, does anybody know another way to trigger a reset on one >>>>> of these systems? I'm told that there is a CMOS reset byte, and that it >>>>> may be possible to write a value to it that causes the "soft" power >>>>> button on the Optiplex to cause a reset instead of a power off. I have >>>>> not investigated this yet, as I'd rather just get a different machine. >>>>> >>>>> >>>>> Thanks, >>>>> -Jon >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------- >>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>>> challenge >>>>> Build the coolest Linux based applications with Moblin SDK & win great >>>>> prizes >>>>> Grand prize is a trip for two to an Open Source event anywhere in the >>>>> world >>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>>> <http://moblin-contest.org/redirect.php?banner_id=100&url=/> >>>>> _______________________________________________ >>>>> tboot-devel mailing list >>>>> tboot-devel@li... >>>>> https://lists.sourceforge.net/lists/listinfo/tboot-devel >>>>> >>>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> ------------------------------------------------------------------------- >>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>> challenge >>>> Build the coolest Linux based applications with Moblin SDK & win great >>>> prizes >>>> Grand prize is a trip for two to an Open Source event anywhere in the >>>> world >>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>> ------------------------------------------------------------------------ >>>> >>>> _______________________________________________ >>>> tboot-devel mailing list >>>> tbo...@li... >>>> https://lists.sourceforge.net/lists/listinfo/tboot-devel >>>> >>>> >>> >>> >> >> > > |
|
From: Jonathan M. M. <jon...@cm...> - 2008-11-10 18:18:28
|
Hi Karthik, Thanks for the quick response. Intel, are there SINIT modules available for these systems? Are they shipping with SINIT modules as part of the BIOS? Thanks, -Jon Karthik . wrote: > Hi Jon > > As far as I know, the new 2008 Elitebook platforms from HP support > TXT/Tboot feature. > > http://h10010.www1.hp.com/wwpc/us/en/sm/WF25a/321957-321957-64295-3740645-89315-3688868.html > http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-3740645-3329741-3782310.html > http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-3740645-3329741-3784202.html > http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-3740645-306995-3784558-3784561-3802771.html > http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-3740645-306995-3782222-3782253-3782268.html > > Thanks > Karthik > > > > On Mon, Nov 10, 2008 at 11:27 AM, Jonathan M. McCune <jon...@cm...> wrote: > >> Hi Karthik, tboot-devel, >> >> Any news on the HP BIOS? >> >> Are there any laptops available yet that support tboot? I seem to remember a >> post from Joe explaining when they might become available but I've been >> unable to locate it. >> >> A search on newegg.com for laptops with vPro turns up several machines. >> Lenovo and Toshiba seem to be using an M45 chipset. ASUS has one with a >> GM965. My understanding is still that Q35 and X38 are the only ones that >> work today. >> >> Thanks! >> -Jon >> >> >> >> Karthik . wrote: >> >>> HP Desktop Bios team is working on this issue and may release it in couple >>> of weeks. Thanks >>> >>> Karthik >>> >>> >>> *Re: [tboot-devel] Buying a machine that will actually work with TXT* >>> From: Jonathan M. McCune <jonmccune@cm...> - 2008-10-09 17:18 >>> fyi... >>> >>> It seems that the HP Compaq dc7800 does _not_ include a reset button >>> either. >>> >>> -Jon >>> >>> >>> Jonathan M. McCune wrote: >>> >>>> Hal Finney wrote: >>>> >>>>> When Trusted Execution was announced, 3 models of computers were >>>>> identified as supporting it: The HP Compaq dc7800, Dell OptiPlex 755 >>>>> PC, and the Lenovo ThinkCentre M57p. I don't know of any others that >>>>> have been added to that list since then. >>>>> >>>>> >>>> Does anybody know whether the HP or Lenovo systems include a reset >>>> button? At least the Ultra Slim Form Factor Optiplex 755s have no reset >>>> button, meaning that debugging a system hang requires a power cycle that >>>> clears LT.ERRORCODE, making debugging substantially more difficult. >>>> >>>> >>>> Alternatively, does anybody know another way to trigger a reset on one >>>> of these systems? I'm told that there is a CMOS reset byte, and that it >>>> may be possible to write a value to it that causes the "soft" power >>>> button on the Optiplex to cause a reset instead of a power off. I have >>>> not investigated this yet, as I'd rather just get a different machine. >>>> >>>> >>>> Thanks, >>>> -Jon >>>> >>>> >>>> >>>> ------------------------------------------------------------------------- >>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>> challenge >>>> Build the coolest Linux based applications with Moblin SDK & win great >>>> prizes >>>> Grand prize is a trip for two to an Open Source event anywhere in the >>>> world >>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>> <http://moblin-contest.org/redirect.php?banner_id=100&url=/> >>>> _______________________________________________ >>>> tboot-devel mailing list >>>> tboot-devel@li... >>>> https://lists.sourceforge.net/lists/listinfo/tboot-devel >>>> >>>> >>> ------------------------------------------------------------------------ >>> >>> ------------------------------------------------------------------------- >>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>> challenge >>> Build the coolest Linux based applications with Moblin SDK & win great >>> prizes >>> Grand prize is a trip for two to an Open Source event anywhere in the >>> world >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> tboot-devel mailing list >>> tbo...@li... >>> https://lists.sourceforge.net/lists/listinfo/tboot-devel >>> >>> >> > > |
|
From: Karthik . <tr...@gm...> - 2008-11-10 18:05:29
|
Hi Jon As far as I know, the new 2008 Elitebook platforms from HP support TXT/Tboot feature. http://h10010.www1.hp.com/wwpc/us/en/sm/WF25a/321957-321957-64295-3740645-89315-3688868.html http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-3740645-3329741-3782310.html http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/321957-321957-64295-3740645-3329741-3784202.html http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-3740645-306995-3784558-3784561-3802771.html http://h10010.www1.hp.com/wwpc/us/en/sm/WF06b/321957-321957-64295-3740645-306995-3782222-3782253-3782268.html Thanks Karthik On Mon, Nov 10, 2008 at 11:27 AM, Jonathan M. McCune <jon...@cm...> wrote: > Hi Karthik, tboot-devel, > > Any news on the HP BIOS? > > Are there any laptops available yet that support tboot? I seem to remember a > post from Joe explaining when they might become available but I've been > unable to locate it. > > A search on newegg.com for laptops with vPro turns up several machines. > Lenovo and Toshiba seem to be using an M45 chipset. ASUS has one with a > GM965. My understanding is still that Q35 and X38 are the only ones that > work today. > > Thanks! > -Jon > > > > Karthik . wrote: >> >> HP Desktop Bios team is working on this issue and may release it in couple >> of weeks. Thanks >> >> Karthik >> >> >> *Re: [tboot-devel] Buying a machine that will actually work with TXT* >> From: Jonathan M. McCune <jonmccune@cm...> - 2008-10-09 17:18 >> fyi... >> >> It seems that the HP Compaq dc7800 does _not_ include a reset button >> either. >> >> -Jon >> >> >> Jonathan M. McCune wrote: >> > Hal Finney wrote: >> >> When Trusted Execution was announced, 3 models of computers were >> >> identified as supporting it: The HP Compaq dc7800, Dell OptiPlex 755 >> >> PC, and the Lenovo ThinkCentre M57p. I don't know of any others that >> >> have been added to that list since then. >> >> >> > >> > Does anybody know whether the HP or Lenovo systems include a reset >> > button? At least the Ultra Slim Form Factor Optiplex 755s have no reset >> > button, meaning that debugging a system hang requires a power cycle that >> > clears LT.ERRORCODE, making debugging substantially more difficult. >> > >> > >> > Alternatively, does anybody know another way to trigger a reset on one >> > of these systems? I'm told that there is a CMOS reset byte, and that it >> > may be possible to write a value to it that causes the "soft" power >> > button on the Optiplex to cause a reset instead of a power off. I have >> > not investigated this yet, as I'd rather just get a different machine. >> > >> > >> > Thanks, >> > -Jon >> > >> > >> > >> > ------------------------------------------------------------------------- >> > This SF.Net email is sponsored by the Moblin Your Move Developer's >> > challenge >> > Build the coolest Linux based applications with Moblin SDK & win great >> > prizes >> > Grand prize is a trip for two to an Open Source event anywhere in the >> > world >> > http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> > <http://moblin-contest.org/redirect.php?banner_id=100&url=/> >> > _______________________________________________ >> > tboot-devel mailing list >> > tboot-devel@li... >> > https://lists.sourceforge.net/lists/listinfo/tboot-devel >> > >> >> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> tboot-devel mailing list >> tbo...@li... >> https://lists.sourceforge.net/lists/listinfo/tboot-devel >> > > |
|
From: Jonathan M. M. <jon...@cm...> - 2008-11-10 17:27:28
|
Hi Karthik, tboot-devel, Any news on the HP BIOS? Are there any laptops available yet that support tboot? I seem to remember a post from Joe explaining when they might become available but I've been unable to locate it. A search on newegg.com for laptops with vPro turns up several machines. Lenovo and Toshiba seem to be using an M45 chipset. ASUS has one with a GM965. My understanding is still that Q35 and X38 are the only ones that work today. Thanks! -Jon Karthik . wrote: > HP Desktop Bios team is working on this issue and may release it in > couple of weeks. Thanks > > Karthik > > > *Re: [tboot-devel] Buying a machine that will actually work with TXT* > From: Jonathan M. McCune <jonmccune@cm...> - 2008-10-09 17:18 > fyi... > > It seems that the HP Compaq dc7800 does _not_ include a reset button > either. > > -Jon > > > Jonathan M. McCune wrote: > > Hal Finney wrote: > >> When Trusted Execution was announced, 3 models of computers were > >> identified as supporting it: The HP Compaq dc7800, Dell OptiPlex 755 > >> PC, and the Lenovo ThinkCentre M57p. I don't know of any others that > >> have been added to that list since then. > >> > > > > Does anybody know whether the HP or Lenovo systems include a reset > > button? At least the Ultra Slim Form Factor Optiplex 755s have no reset > > button, meaning that debugging a system hang requires a power cycle > that > > clears LT.ERRORCODE, making debugging substantially more difficult. > > > > > > Alternatively, does anybody know another way to trigger a reset on one > > of these systems? I'm told that there is a CMOS reset byte, and that it > > may be possible to write a value to it that causes the "soft" power > > button on the Optiplex to cause a reset instead of a power off. I have > > not investigated this yet, as I'd rather just get a different machine. > > > > > > Thanks, > > -Jon > > > > > > > ------------------------------------------------------------------------- > > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > > Build the coolest Linux based applications with Moblin SDK & win > great prizes > > Grand prize is a trip for two to an Open Source event anywhere in > the world > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > <http://moblin-contest.org/redirect.php?banner_id=100&url=/> > > _______________________________________________ > > tboot-devel mailing list > > tboot-devel@li... > > https://lists.sourceforge.net/lists/listinfo/tboot-devel > > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ------------------------------------------------------------------------ > > _______________________________________________ > tboot-devel mailing list > tbo...@li... > https://lists.sourceforge.net/lists/listinfo/tboot-devel > |
|
From: Lil E. <Lil...@gm...> - 2008-11-05 09:42:20
|
Hi, you can try either using AMT serial console, which will give you other headaches, or you can get your hands on a docking station which exports the serial interface (if your manufacturer offers such a thing). Saves you lots of pain. Cheers lIl -------- Original-Nachricht -------- > Datum: Mon, 3 Nov 2008 14:14:29 -0500 > Von: "Ross Philipson" <Ros...@ci...> > An: tbo...@li... > Betreff: [tboot-devel] Enhance serial support in tboot > I have recently been working on laptops that do not have serial ports so > I have been using an ExpressCard serial adapter. I had to make > modification to tboot to use a different IO port and clock frequency. I > have found that having serial debug output for tboot is incredibly > valuable during development. > > > > The Xen console driver (on which the tboot early_printk is loosely based > as it seems) allows serial console configuration with command line > arguments (including setting the clock freq. now). I was thinking of > pulling this into tboot but I wanted to see if the community thought > this was something valuable to do - something that could be incorporated > in tboot? > > > > Thanks > > Ross > > > > Ross Philipson > > Senior Software Engineer > > Citrix Systems, Inc > > 14 Crosby Drive > > Bedford, MA 01730 > > 781-301-7949 > > ros...@ci... <mailto:ros...@ci...> > > > -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger |
|
From: Ross P. <Ros...@ci...> - 2008-11-03 19:17:46
|
I have recently been working on laptops that do not have serial ports so I have been using an ExpressCard serial adapter. I had to make modification to tboot to use a different IO port and clock frequency. I have found that having serial debug output for tboot is incredibly valuable during development. The Xen console driver (on which the tboot early_printk is loosely based as it seems) allows serial console configuration with command line arguments (including setting the clock freq. now). I was thinking of pulling this into tboot but I wanted to see if the community thought this was something valuable to do - something that could be incorporated in tboot? Thanks Ross Ross Philipson Senior Software Engineer Citrix Systems, Inc 14 Crosby Drive Bedford, MA 01730 781-301-7949 ros...@ci... <mailto:ros...@ci...> |
|
From: Wang, S. <sha...@in...> - 2008-10-22 02:07:41
|
No. I just want to see what kind of debug tool you can use? then to determine how to debug it. Only printk on serial port? I just want to see whether the program runs into tboot_shutdown() in xen/arch/x86/tboot.c when you do poweroff or reboot. >From the result of your poweroff, it is obvious it rans into the function. >From the result of your reboot, if it didn't, or if it did but it map_pages_to_xen() wrongly, sexit will not be invoked. Anyway, I will try it again first on my side. Shane Lil Evil wrote: > Hi Shane, > > Not sure what you mean by debugging tools available?? > Do you mean what I am using to get those error messages? > I haven't chased this issue up recently as I have been busy. > please find the xen debug output attached to this mail. > > cheers > lIl > > > -------- Original-Nachricht -------- >> Datum: Tue, 21 Oct 2008 16:25:37 +0800 >> Von: "Wang, Shane" <sha...@in...> >> An: Lil Evil <Lil...@gm...>, "tbo...@li..." >> <tbo...@li...> Betreff: RE: [tboot-devel] new >> location for mercurial repo > >> If poweroff can do but reboot can't, it is strange. >> >> Can you output Xen messages on the serial port? >> And by the way, tell me which debug tools are available for you, >> besides >> serial port? >> >> Lil Evil wrote: >>> -------- Original-Nachricht -------- >>>> Datum: Thu, 9 Oct 2008 09:47:03 -0700 >>>> Von: "Cihula, Joseph" <jos...@in...> >>>> An: "Lil Evil" <Lil...@gm...>, tbo...@li... >>>> Betreff: RE: [tboot-devel] new location for mercurial repo >>> >>>>> From: Lil Evil [mailto:Lil...@gm...] >>>>> Sent: Thursday, October 09, 2008 3:21 AM >>>>> >>>>> Hi, >>>>> >>>>> okay verification works now fine. Must have skipped that part in >>>>> the README :). >>>>> >>>>> I said broadcasted, because I assumed that it hasn't indeed been >>>>> broadcasted. Meaning it didn't show up on the serial console. >>>>> As I said it showed up during powering off, but not during >>>>> rebooting. >>>> >>>> Can you send me the serial output? And what system is this? >>> >>> Machine is a HP DC7800 bios v1.26 >>> tboot stable (version 2008613) and tboot.hg (revision 85), both >>> show the same behaviour. >>> >>> tboot & verfication successful >>> >>> -> reboot doesn't execute getsec[sexit] >>> -> machine hangs ( black screen ) >>> see tboot_reboot.txt >>> >>> -> powerdown does execute getsec[sexit] >>> see tboot_poweroff.txt >>> I can see the getsec[sexit] here... >>> >>> >>> >>>> >>>>> However, if I issue a reboot, the machine will hang with no screen >>>>> at all. Only a hard reset brings it back to life. >>>>> Hence, I assumed that TXT is protecting the machine, because it >>>>> hasn't successfully issued SEXIT. But, it also could be an issue >>>>> of my machine's BIOS, as I already encountered some. >>>> >>>> This sounds like SEXIT is not finishing. Typical reasons for that >>>> are if not all of the CPUs got woken up or if some still had VMX >>>> on. >>>> >>>>> >>>>> I keep on playing around and let you know what's happening. >>>>> >>>>> Cheers >>>>> lIl >>>>> >>>>> >>>>> -------- Original-Nachricht -------- >>>>>> Datum: Wed, 8 Oct 2008 11:26:51 -0700 >>>>>> Von: "Cihula, Joseph" <jos...@in...> >>>>>> An: "Lil Evil" <Lil...@gm...>, >>>>>> tbo...@li... Betreff: RE: [tboot-devel] new >>>>>> location for mercurial repo >>>>> >>>>>>> From: Lil Evil [mailto:Lil...@gm...] >>>>>>> Sent: Wednesday, October 08, 2008 2:11 AM >>>>>>> >>>>>>> 1) Compilation >>>>>>> to reproduce the compilation error, I did the following: >>>>>>> >>>>>>> [root@lil staging] hg clone >>>>> http://www.bughost.org/repos.hg/tboot.hg >>>>>>> destination directory: tboot.hg >>>>>>> requesting all changes >>>>>>> adding changesets >>>>>>> adding manifests >>>>>>> adding file changes >>>>>>> added 91 changesets with 393 changes to 122 files >>>>>>> updating working directory >>>>>>> 118 files updated, 0 files merged, 0 files removed, 0 files >>>>>>> unresolved [root@lil staging] cd tboot.hg >>>>>>> [root@lil tboot.hg] make >>>>>>> ... >>>>>>> <compile> >>>>>>> ... >>>>>>> >>>>>>> mlehash.c:47:34: error: ../include/elf_defns.h: No such file or >>>>>>> directory >>>>>>> >>>>>>> >>>>>>> [root@lil tboot.hg]# ls -la include/elf_defns.h >>>>>>> ls: cannot access include/elf_defns.h: No such file or >>>>>>> directory [root@lil tboot.hg]# >>>>>>> >>>>>>> hg reports the following changeset: >>>>>>> >>>>>>> changeset: 90:5d19b96f7c0e >>>>>>> tag: tip >>>>>>> user: Joseph Cihula <jos...@in...> >>>>>>> date: Tue Oct 07 12:03:27 2008 -0700 >>>>>>> summary: Added hg repo location to README >>>>>>> >>>>>>> I tried two different machines on different networks, same >>>>>>> error. which changeset are you on? >>>>>> >>>>>> OK, my bad (I only re-built tboot and not the tools). I have >>>>>> fixed this in the tip and uploaded a new tarfile. >>>>>> >>>>>>> 2) I already adopted to the new policy format already, as I have >>>>>>> been playing around with the mercurial repository a while ago. >>>>>>> The debug line I added, just prints out the PCR before >>>>>>> extending. I was a little bit surprised to see a none 0 row >>>>>>> there. >>>>>>> Something is fishy, either with me, or the build :) >>>>>>> >>>>>>> here is my policy gen script, btw: >>>>>>> >>>>>>> modprobe tpm_tis >>>>>>> tcsd >>>>>>> rm -rf mle_hash lcp.pol vl.pol >>>>>>> >>>>>>> >>>>>>> #create hash of tboot >>>>>>> lcp_mlehash /boot/tboot.gz > mle_hash >>>>>>> >>>>>>> # transform hash into policy >>>>>>> lcp_crtpol -t hashonly -m mle_hash -o lcp.pol >>>>>>> >>>>>>> XENLINE="/xen.gz tboot=0x01019040 iommu=1 vtd=1 dom0_mem=1024mb >>>>>>> com1=1115200,8n1 console=vga,com1" >>>>>>> KERNEL="/vmlinuz-2.6.18.8-xen_unstable ro >>>>>>> root=/dev/VolGroup01/LogVol01 rhgb >>>>>>> pciback.hide=(00:1d.7)(00:1d.1)" >>>>>>> TPM_PW="" >>>>>> >>>>>> The new policy code strips the module name from the module string >>>>>> provided by GRUB so that location isn't part of the measurement >>>>>> (which it shouldn't be). Thus, you should not have '/xen.gz ' or >>>>>> '/vmlinuz-2.6.18.8-xen_unstable ' in your strings. >>>>>> >>>>>>> #create launch policy of the VMM >>>>>>> tb_polgen --create --type nonfatal vl.pol >>>>>>> >>>>>>> tb_polgen --add --num 0 --pcr 18 --hash image --cmdline >>>>>>> "$XENLINE" -- image /boot/xen.gz vl.pol --verbose >> verbose.txt >>>>>>> tb_polgen --add --num 1 --pcr 19 --hash image --cmdline >>>>>>> "$KERNEL" - - image /boot/vmlinuz-2.6.18.8-xen_unstable vl.pol >>>>>>> --verbose >> verbose.txt tb_polgen --add --num 2 --pcr 19 >>>>>>> --hash image --cmdline "" --image >>>>>>> /boot/initrd-2.6.18.8-xen_unstable.img vl.pol --verbose >> >>>>>>> verbose.txt >>>>>>> >>>>>>> #write policy >>>>>>> lcp_writepol -i owner -f lcp.pol -p >>>>>>> lcp_writepol -i 0x20000001 -f vl.pol -p >>>>>>> >>>>>>> >>>>>>> 3) I also noticed with the stable tboot, on a reboot the >>>>>>> GETSEC[SEXIT] command is not broadcasted. It is however on a >>>>>>> shutdown. >>>>>> >>>>>> When you say "broadcasted" do you mean it doesn't appear on the >>>>>> serial output? That is likely just due to buffering and when/how >>>>>> the platform actually disables the serial port. If SEXIT were >>>>>> not done, the system could not reboot successfully (it would >>>>>> TXT_RESET and then the subsequent boot could not launch TXT >>>>>> until a power cycle). >>>>>> >>>>>>> Just to let you know where I am standing at the moment. >>>>>> >>>>>> Thanks for your comments and we'll try to keep things fixed up >>>>>> better. >>>>>> >>>>>>> Cheers >>>>>>> lIl >>>>>>> >>>>>>> -- >>>>>>> Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu >>>>>>> sparen! Ideal für Modem und ISDN: >>>>>>> http://www.gmx.net/de/go/smartsurfer >>>>> >>>>> -- >>>>> Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! >>>>> Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer >>>>> >>>>> >> ----------------------------------------------------------------------- >>>>> -- This SF.Net email is sponsored by the Moblin Your Move >>>>> Developer's challenge Build the coolest Linux based applications >>>>> with Moblin SDK & win great prizes Grand prize is a trip for two >>>>> to an Open Source event anywhere in the world >>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>>> _______________________________________________ >>>>> tboot-devel mailing list >>>>> tbo...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/tboot-devel |
|
From: Lil E. <Lil...@gm...> - 2008-10-21 13:58:03
|
Hi Shane, Not sure what you mean by debugging tools available?? Do you mean what I am using to get those error messages? I haven't chased this issue up recently as I have been busy. please find the xen debug output attached to this mail. cheers lIl -------- Original-Nachricht -------- > Datum: Tue, 21 Oct 2008 16:25:37 +0800 > Von: "Wang, Shane" <sha...@in...> > An: Lil Evil <Lil...@gm...>, "tbo...@li..." <tbo...@li...> > Betreff: RE: [tboot-devel] new location for mercurial repo > If poweroff can do but reboot can't, it is strange. > > Can you output Xen messages on the serial port? > And by the way, tell me which debug tools are available for you, besides > serial port? > > Lil Evil wrote: > > -------- Original-Nachricht -------- > >> Datum: Thu, 9 Oct 2008 09:47:03 -0700 > >> Von: "Cihula, Joseph" <jos...@in...> > >> An: "Lil Evil" <Lil...@gm...>, tbo...@li... > >> Betreff: RE: [tboot-devel] new location for mercurial repo > > > >>> From: Lil Evil [mailto:Lil...@gm...] > >>> Sent: Thursday, October 09, 2008 3:21 AM > >>> > >>> Hi, > >>> > >>> okay verification works now fine. Must have skipped that part in > >>> the README :). > >>> > >>> I said broadcasted, because I assumed that it hasn't indeed been > >>> broadcasted. Meaning it didn't show up on the serial console. > >>> As I said it showed up during powering off, but not during > >>> rebooting. > >> > >> Can you send me the serial output? And what system is this? > > > > Machine is a HP DC7800 bios v1.26 > > tboot stable (version 2008613) and tboot.hg (revision 85), both show > > the same behaviour. > > > > tboot & verfication successful > > > > -> reboot doesn't execute getsec[sexit] > > -> machine hangs ( black screen ) > > see tboot_reboot.txt > > > > -> powerdown does execute getsec[sexit] > > see tboot_poweroff.txt > > I can see the getsec[sexit] here... > > > > > > > >> > >>> However, if I issue a reboot, the machine will hang with no screen > >>> at all. Only a hard reset brings it back to life. > >>> Hence, I assumed that TXT is protecting the machine, because it > >>> hasn't successfully issued SEXIT. But, it also could be an issue of > >>> my machine's BIOS, as I already encountered some. > >> > >> This sounds like SEXIT is not finishing. Typical reasons for that > >> are if not all of the CPUs got woken up or if some still had VMX on. > >> > >>> > >>> I keep on playing around and let you know what's happening. > >>> > >>> Cheers > >>> lIl > >>> > >>> > >>> -------- Original-Nachricht -------- > >>>> Datum: Wed, 8 Oct 2008 11:26:51 -0700 > >>>> Von: "Cihula, Joseph" <jos...@in...> > >>>> An: "Lil Evil" <Lil...@gm...>, tbo...@li... > >>>> Betreff: RE: [tboot-devel] new location for mercurial repo > >>> > >>>>> From: Lil Evil [mailto:Lil...@gm...] > >>>>> Sent: Wednesday, October 08, 2008 2:11 AM > >>>>> > >>>>> 1) Compilation > >>>>> to reproduce the compilation error, I did the following: > >>>>> > >>>>> [root@lil staging] hg clone > >>> http://www.bughost.org/repos.hg/tboot.hg > >>>>> destination directory: tboot.hg > >>>>> requesting all changes > >>>>> adding changesets > >>>>> adding manifests > >>>>> adding file changes > >>>>> added 91 changesets with 393 changes to 122 files > >>>>> updating working directory > >>>>> 118 files updated, 0 files merged, 0 files removed, 0 files > >>>>> unresolved [root@lil staging] cd tboot.hg > >>>>> [root@lil tboot.hg] make > >>>>> ... > >>>>> <compile> > >>>>> ... > >>>>> > >>>>> mlehash.c:47:34: error: ../include/elf_defns.h: No such file or > >>>>> directory > >>>>> > >>>>> > >>>>> [root@lil tboot.hg]# ls -la include/elf_defns.h > >>>>> ls: cannot access include/elf_defns.h: No such file or directory > >>>>> [root@lil tboot.hg]# > >>>>> > >>>>> hg reports the following changeset: > >>>>> > >>>>> changeset: 90:5d19b96f7c0e > >>>>> tag: tip > >>>>> user: Joseph Cihula <jos...@in...> > >>>>> date: Tue Oct 07 12:03:27 2008 -0700 > >>>>> summary: Added hg repo location to README > >>>>> > >>>>> I tried two different machines on different networks, same error. > >>>>> which changeset are you on? > >>>> > >>>> OK, my bad (I only re-built tboot and not the tools). I have > >>>> fixed this in the tip and uploaded a new tarfile. > >>>> > >>>>> 2) I already adopted to the new policy format already, as I have > >>>>> been playing around with the mercurial repository a while ago. > >>>>> The debug line I added, just prints out the PCR before extending. > >>>>> I was a little bit surprised to see a none 0 row there. > >>>>> Something is fishy, either with me, or the build :) > >>>>> > >>>>> here is my policy gen script, btw: > >>>>> > >>>>> modprobe tpm_tis > >>>>> tcsd > >>>>> rm -rf mle_hash lcp.pol vl.pol > >>>>> > >>>>> > >>>>> #create hash of tboot > >>>>> lcp_mlehash /boot/tboot.gz > mle_hash > >>>>> > >>>>> # transform hash into policy > >>>>> lcp_crtpol -t hashonly -m mle_hash -o lcp.pol > >>>>> > >>>>> XENLINE="/xen.gz tboot=0x01019040 iommu=1 vtd=1 dom0_mem=1024mb > >>>>> com1=1115200,8n1 console=vga,com1" > >>>>> KERNEL="/vmlinuz-2.6.18.8-xen_unstable ro > >>>>> root=/dev/VolGroup01/LogVol01 rhgb > >>>>> pciback.hide=(00:1d.7)(00:1d.1)" > >>>>> TPM_PW="" > >>>> > >>>> The new policy code strips the module name from the module string > >>>> provided by GRUB so that location isn't part of the measurement > >>>> (which it shouldn't be). Thus, you should not have '/xen.gz ' or > >>>> '/vmlinuz-2.6.18.8-xen_unstable ' in your strings. > >>>> > >>>>> #create launch policy of the VMM > >>>>> tb_polgen --create --type nonfatal vl.pol > >>>>> > >>>>> tb_polgen --add --num 0 --pcr 18 --hash image --cmdline > >>>>> "$XENLINE" -- image /boot/xen.gz vl.pol --verbose >> verbose.txt > >>>>> tb_polgen --add --num 1 --pcr 19 --hash image --cmdline "$KERNEL" > >>>>> - - image /boot/vmlinuz-2.6.18.8-xen_unstable vl.pol --verbose >> > >>>>> verbose.txt tb_polgen --add --num 2 --pcr 19 --hash image > >>>>> --cmdline "" --image /boot/initrd-2.6.18.8-xen_unstable.img > >>>>> vl.pol --verbose >> verbose.txt > >>>>> > >>>>> #write policy > >>>>> lcp_writepol -i owner -f lcp.pol -p > >>>>> lcp_writepol -i 0x20000001 -f vl.pol -p > >>>>> > >>>>> > >>>>> 3) I also noticed with the stable tboot, on a reboot the > >>>>> GETSEC[SEXIT] command is not broadcasted. It is however on a > >>>>> shutdown. > >>>> > >>>> When you say "broadcasted" do you mean it doesn't appear on the > >>>> serial output? That is likely just due to buffering and when/how > >>>> the platform actually disables the serial port. If SEXIT were not > >>>> done, the system could not reboot successfully (it would TXT_RESET > >>>> and then the subsequent boot could not launch TXT until a power > >>>> cycle). > >>>> > >>>>> Just to let you know where I am standing at the moment. > >>>> > >>>> Thanks for your comments and we'll try to keep things fixed up > >>>> better. > >>>> > >>>>> Cheers > >>>>> lIl > >>>>> > >>>>> -- > >>>>> Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! > >>>>> Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer > >>> > >>> -- > >>> Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! > >>> Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer > >>> > >>> > ----------------------------------------------------------------------- > >>> -- This SF.Net email is sponsored by the Moblin Your Move > >>> Developer's challenge Build the coolest Linux based applications > >>> with Moblin SDK & win great prizes Grand prize is a trip for two to > >>> an Open Source event anywhere in the world > >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >>> _______________________________________________ > >>> tboot-devel mailing list > >>> tbo...@li... > >>> https://lists.sourceforge.net/lists/listinfo/tboot-devel -- GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit Pastry Passion! http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/6169196 |
|
From: Wang, S. <sha...@in...> - 2008-10-21 08:29:55
|
If poweroff can do but reboot can't, it is strange. Can you output Xen messages on the serial port? And by the way, tell me which debug tools are available for you, besides serial port? Lil Evil wrote: > -------- Original-Nachricht -------- >> Datum: Thu, 9 Oct 2008 09:47:03 -0700 >> Von: "Cihula, Joseph" <jos...@in...> >> An: "Lil Evil" <Lil...@gm...>, tbo...@li... >> Betreff: RE: [tboot-devel] new location for mercurial repo > >>> From: Lil Evil [mailto:Lil...@gm...] >>> Sent: Thursday, October 09, 2008 3:21 AM >>> >>> Hi, >>> >>> okay verification works now fine. Must have skipped that part in >>> the README :). >>> >>> I said broadcasted, because I assumed that it hasn't indeed been >>> broadcasted. Meaning it didn't show up on the serial console. >>> As I said it showed up during powering off, but not during >>> rebooting. >> >> Can you send me the serial output? And what system is this? > > Machine is a HP DC7800 bios v1.26 > tboot stable (version 2008613) and tboot.hg (revision 85), both show > the same behaviour. > > tboot & verfication successful > > -> reboot doesn't execute getsec[sexit] > -> machine hangs ( black screen ) > see tboot_reboot.txt > > -> powerdown does execute getsec[sexit] > see tboot_poweroff.txt > I can see the getsec[sexit] here... > > > >> >>> However, if I issue a reboot, the machine will hang with no screen >>> at all. Only a hard reset brings it back to life. >>> Hence, I assumed that TXT is protecting the machine, because it >>> hasn't successfully issued SEXIT. But, it also could be an issue of >>> my machine's BIOS, as I already encountered some. >> >> This sounds like SEXIT is not finishing. Typical reasons for that >> are if not all of the CPUs got woken up or if some still had VMX on. >> >>> >>> I keep on playing around and let you know what's happening. >>> >>> Cheers >>> lIl >>> >>> >>> -------- Original-Nachricht -------- >>>> Datum: Wed, 8 Oct 2008 11:26:51 -0700 >>>> Von: "Cihula, Joseph" <jos...@in...> >>>> An: "Lil Evil" <Lil...@gm...>, tbo...@li... >>>> Betreff: RE: [tboot-devel] new location for mercurial repo >>> >>>>> From: Lil Evil [mailto:Lil...@gm...] >>>>> Sent: Wednesday, October 08, 2008 2:11 AM >>>>> >>>>> 1) Compilation >>>>> to reproduce the compilation error, I did the following: >>>>> >>>>> [root@lil staging] hg clone >>> http://www.bughost.org/repos.hg/tboot.hg >>>>> destination directory: tboot.hg >>>>> requesting all changes >>>>> adding changesets >>>>> adding manifests >>>>> adding file changes >>>>> added 91 changesets with 393 changes to 122 files >>>>> updating working directory >>>>> 118 files updated, 0 files merged, 0 files removed, 0 files >>>>> unresolved [root@lil staging] cd tboot.hg >>>>> [root@lil tboot.hg] make >>>>> ... >>>>> <compile> >>>>> ... >>>>> >>>>> mlehash.c:47:34: error: ../include/elf_defns.h: No such file or >>>>> directory >>>>> >>>>> >>>>> [root@lil tboot.hg]# ls -la include/elf_defns.h >>>>> ls: cannot access include/elf_defns.h: No such file or directory >>>>> [root@lil tboot.hg]# >>>>> >>>>> hg reports the following changeset: >>>>> >>>>> changeset: 90:5d19b96f7c0e >>>>> tag: tip >>>>> user: Joseph Cihula <jos...@in...> >>>>> date: Tue Oct 07 12:03:27 2008 -0700 >>>>> summary: Added hg repo location to README >>>>> >>>>> I tried two different machines on different networks, same error. >>>>> which changeset are you on? >>>> >>>> OK, my bad (I only re-built tboot and not the tools). I have >>>> fixed this in the tip and uploaded a new tarfile. >>>> >>>>> 2) I already adopted to the new policy format already, as I have >>>>> been playing around with the mercurial repository a while ago. >>>>> The debug line I added, just prints out the PCR before extending. >>>>> I was a little bit surprised to see a none 0 row there. >>>>> Something is fishy, either with me, or the build :) >>>>> >>>>> here is my policy gen script, btw: >>>>> >>>>> modprobe tpm_tis >>>>> tcsd >>>>> rm -rf mle_hash lcp.pol vl.pol >>>>> >>>>> >>>>> #create hash of tboot >>>>> lcp_mlehash /boot/tboot.gz > mle_hash >>>>> >>>>> # transform hash into policy >>>>> lcp_crtpol -t hashonly -m mle_hash -o lcp.pol >>>>> >>>>> XENLINE="/xen.gz tboot=0x01019040 iommu=1 vtd=1 dom0_mem=1024mb >>>>> com1=1115200,8n1 console=vga,com1" >>>>> KERNEL="/vmlinuz-2.6.18.8-xen_unstable ro >>>>> root=/dev/VolGroup01/LogVol01 rhgb >>>>> pciback.hide=(00:1d.7)(00:1d.1)" >>>>> TPM_PW="" >>>> >>>> The new policy code strips the module name from the module string >>>> provided by GRUB so that location isn't part of the measurement >>>> (which it shouldn't be). Thus, you should not have '/xen.gz ' or >>>> '/vmlinuz-2.6.18.8-xen_unstable ' in your strings. >>>> >>>>> #create launch policy of the VMM >>>>> tb_polgen --create --type nonfatal vl.pol >>>>> >>>>> tb_polgen --add --num 0 --pcr 18 --hash image --cmdline >>>>> "$XENLINE" -- image /boot/xen.gz vl.pol --verbose >> verbose.txt >>>>> tb_polgen --add --num 1 --pcr 19 --hash image --cmdline "$KERNEL" >>>>> - - image /boot/vmlinuz-2.6.18.8-xen_unstable vl.pol --verbose >> >>>>> verbose.txt tb_polgen --add --num 2 --pcr 19 --hash image >>>>> --cmdline "" --image /boot/initrd-2.6.18.8-xen_unstable.img >>>>> vl.pol --verbose >> verbose.txt >>>>> >>>>> #write policy >>>>> lcp_writepol -i owner -f lcp.pol -p >>>>> lcp_writepol -i 0x20000001 -f vl.pol -p >>>>> >>>>> >>>>> 3) I also noticed with the stable tboot, on a reboot the >>>>> GETSEC[SEXIT] command is not broadcasted. It is however on a >>>>> shutdown. >>>> >>>> When you say "broadcasted" do you mean it doesn't appear on the >>>> serial output? That is likely just due to buffering and when/how >>>> the platform actually disables the serial port. If SEXIT were not >>>> done, the system could not reboot successfully (it would TXT_RESET >>>> and then the subsequent boot could not launch TXT until a power >>>> cycle). >>>> >>>>> Just to let you know where I am standing at the moment. >>>> >>>> Thanks for your comments and we'll try to keep things fixed up >>>> better. >>>> >>>>> Cheers >>>>> lIl >>>>> >>>>> -- >>>>> Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! >>>>> Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer >>> >>> -- >>> Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! >>> Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer >>> >>> ----------------------------------------------------------------------- >>> -- This SF.Net email is sponsored by the Moblin Your Move >>> Developer's challenge Build the coolest Linux based applications >>> with Moblin SDK & win great prizes Grand prize is a trip for two to >>> an Open Source event anywhere in the world >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> _______________________________________________ >>> tboot-devel mailing list >>> tbo...@li... >>> https://lists.sourceforge.net/lists/listinfo/tboot-devel |
|
From: Lil E. <Lil...@gm...> - 2008-10-20 12:30:40
|
-------- Original-Nachricht -------- > Datum: Thu, 9 Oct 2008 09:47:03 -0700 > Von: "Cihula, Joseph" <jos...@in...> > An: "Lil Evil" <Lil...@gm...>, tbo...@li... > Betreff: RE: [tboot-devel] new location for mercurial repo > > From: Lil Evil [mailto:Lil...@gm...] > > Sent: Thursday, October 09, 2008 3:21 AM > > > > Hi, > > > > okay verification works now fine. Must have skipped that part in the > > README :). > > > > I said broadcasted, because I assumed that it hasn't indeed been > > broadcasted. > > Meaning it didn't show up on the serial console. > > As I said it showed up during powering off, but not during rebooting. > > Can you send me the serial output? And what system is this? Machine is a HP DC7800 bios v1.26 tboot stable (version 2008613) and tboot.hg (revision 85), both show the same behaviour. tboot & verfication successful -> reboot doesn't execute getsec[sexit] -> machine hangs ( black screen ) see tboot_reboot.txt -> powerdown does execute getsec[sexit] see tboot_poweroff.txt I can see the getsec[sexit] here... > > > However, if I issue a reboot, the machine will hang with no screen at > > all. > > Only a hard reset brings it back to life. > > Hence, I assumed that TXT is protecting the machine, because it hasn't > > successfully issued SEXIT. > > But, it also could be an issue of my machine's BIOS, as I already > > encountered some. > > This sounds like SEXIT is not finishing. Typical reasons for that are if > not all of the CPUs got woken up or if some still had VMX on. > > > > > I keep on playing around and let you know what's happening. > > > > Cheers > > lIl > > > > > > -------- Original-Nachricht -------- > > > Datum: Wed, 8 Oct 2008 11:26:51 -0700 > > > Von: "Cihula, Joseph" <jos...@in...> > > > An: "Lil Evil" <Lil...@gm...>, tbo...@li... > > > Betreff: RE: [tboot-devel] new location for mercurial repo > > > > > > From: Lil Evil [mailto:Lil...@gm...] > > > > Sent: Wednesday, October 08, 2008 2:11 AM > > > > > > > > 1) Compilation > > > > to reproduce the compilation error, I did the following: > > > > > > > > [root@lil staging] hg clone > > http://www.bughost.org/repos.hg/tboot.hg > > > > destination directory: tboot.hg > > > > requesting all changes > > > > adding changesets > > > > adding manifests > > > > adding file changes > > > > added 91 changesets with 393 changes to 122 files > > > > updating working directory > > > > 118 files updated, 0 files merged, 0 files removed, 0 files > > unresolved > > > > [root@lil staging] cd tboot.hg > > > > [root@lil tboot.hg] make > > > > ... > > > > <compile> > > > > ... > > > > > > > > mlehash.c:47:34: error: ../include/elf_defns.h: No such file or > > > > directory > > > > > > > > > > > > [root@lil tboot.hg]# ls -la include/elf_defns.h > > > > ls: cannot access include/elf_defns.h: No such file or directory > > > > [root@lil tboot.hg]# > > > > > > > > hg reports the following changeset: > > > > > > > > changeset: 90:5d19b96f7c0e > > > > tag: tip > > > > user: Joseph Cihula <jos...@in...> > > > > date: Tue Oct 07 12:03:27 2008 -0700 > > > > summary: Added hg repo location to README > > > > > > > > I tried two different machines on different networks, same error. > > > > which changeset are you on? > > > > > > OK, my bad (I only re-built tboot and not the tools). I have fixed > > this > > > in the tip and uploaded a new tarfile. > > > > > > > 2) I already adopted to the new policy format already, as I have > > been > > > > playing around with the mercurial repository a while ago. > > > > The debug line I added, just prints out the PCR before extending. I > > was > > > > a little bit surprised to see a none 0 row there. > > > > Something is fishy, either with me, or the build :) > > > > > > > > here is my policy gen script, btw: > > > > > > > > modprobe tpm_tis > > > > tcsd > > > > rm -rf mle_hash lcp.pol vl.pol > > > > > > > > > > > > #create hash of tboot > > > > lcp_mlehash /boot/tboot.gz > mle_hash > > > > > > > > # transform hash into policy > > > > lcp_crtpol -t hashonly -m mle_hash -o lcp.pol > > > > > > > > XENLINE="/xen.gz tboot=0x01019040 iommu=1 vtd=1 dom0_mem=1024mb > > > > com1=1115200,8n1 console=vga,com1" > > > > KERNEL="/vmlinuz-2.6.18.8-xen_unstable ro > > root=/dev/VolGroup01/LogVol01 > > > > rhgb pciback.hide=(00:1d.7)(00:1d.1)" > > > > TPM_PW="" > > > > > > The new policy code strips the module name from the module string > > provided > > > by GRUB so that location isn't part of the measurement (which it > > shouldn't > > > be). Thus, you should not have '/xen.gz ' or > > > '/vmlinuz-2.6.18.8-xen_unstable ' in your strings. > > > > > > > #create launch policy of the VMM > > > > tb_polgen --create --type nonfatal vl.pol > > > > > > > > tb_polgen --add --num 0 --pcr 18 --hash image --cmdline "$XENLINE" > > -- > > > > image /boot/xen.gz vl.pol --verbose >> verbose.txt > > > > tb_polgen --add --num 1 --pcr 19 --hash image --cmdline "$KERNEL" - > > - > > > > image /boot/vmlinuz-2.6.18.8-xen_unstable vl.pol --verbose >> > > > > verbose.txt > > > > tb_polgen --add --num 2 --pcr 19 --hash image --cmdline "" --image > > > > /boot/initrd-2.6.18.8-xen_unstable.img vl.pol --verbose >> > > verbose.txt > > > > > > > > #write policy > > > > lcp_writepol -i owner -f lcp.pol -p > > > > lcp_writepol -i 0x20000001 -f vl.pol -p > > > > > > > > > > > > 3) I also noticed with the stable tboot, on a reboot the > > GETSEC[SEXIT] > > > > command is not broadcasted. > > > > It is however on a shutdown. > > > > > > When you say "broadcasted" do you mean it doesn't appear on the > > serial > > > output? That is likely just due to buffering and when/how the > > platform > > > actually disables the serial port. If SEXIT were not done, the > > system could not > > > reboot successfully (it would TXT_RESET and then the subsequent boot > > could > > > not launch TXT until a power cycle). > > > > > > > Just to let you know where I am standing at the moment. > > > > > > Thanks for your comments and we'll try to keep things fixed up > > better. > > > > > > > Cheers > > > > lIl > > > > > > > > -- > > > > Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! > > > > Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer > > > > -- > > Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! > > Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer > > > > ----------------------------------------------------------------------- > > -- > > This SF.Net email is sponsored by the Moblin Your Move Developer's > > challenge > > Build the coolest Linux based applications with Moblin SDK & win great > > prizes > > Grand prize is a trip for two to an Open Source event anywhere in the > > world > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > _______________________________________________ > > tboot-devel mailing list > > tbo...@li... > > https://lists.sourceforge.net/lists/listinfo/tboot-devel -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer |
|
From: Cihula, J. <jos...@in...> - 2008-10-14 22:41:56
|
> From: Jonathan M. McCune [mailto:jon...@cm...] > Sent: Tuesday, October 14, 2008 2:51 PM > > Hi Joe, list, > > I'm able to read the registers now, but I'm still not sure what I'm > doing wrong. Details... > > With the latest xen-unstable.hg and tboot.hg, I added some code to > xen/drivers/passthrough/vtd/utils.c:dump_iommu_info() to also dump the > Protected Memory Registers (enable, low base/limit, high base/limit). > I > inserted a call so that these registers get printed before more > sophisticated remapping is enabled. I then printed them again manually > after Xen has fully booted (using 3xCtrl+A, V). > > The 0xfed93000 from my previous email was 4K aligned, but it turns out > that the only DRHD with non-zero PMR registers on my system is > 0xfed91000 (low base of 16MB, size 16MB), and only during boot time > (this makes sense, since disable_pmr() is called for each DRHD): > > (XEN) print_iommu_regs: DMAR_PMEN_REG = 80000001 > (XEN) print_iommu_regs: DMAR_PLMBASE_REG = 1000000 > (XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 1000000 > (XEN) print_iommu_regs: DMAR_PHMBASE_REG = 200000 > (XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0 > > > When I invoke SENTER with my code (on a non-Xen, vanilla Linux system), > I configure the low PMR region to be 2 MB in size, starting at 12 MB of > physical memory (kmalloc()'d). > > TBOOT: os_sinit_data->vtd_pmr_lo_base: 0xc00000 > TBOOT: os_sinit_data->vtd_pmr_lo_size: 0x200000 > TBOOT: os_sinit_data->vtd_pmr_hi_base: 0x0 > TBOOT: os_sinit_data->vtd_pmr_hi_size: 0x0 > > It uses these same memory regions every time, and reliably works once > but then fails (triggering a reboot) with: > > TBOOT: LT.ERRORCODE=c00038f1 > TBOOT: AC module error : acm_type=1, progress=0f, error=e > > 1110 Current values of VT-d PMR registers do not match > requested values in SinitMleData > > > If I try to read the PMR registers between sessions (i.e., while the > system is _not_ in any kind of secure mode; SEXIT _did_ execute > following SENTER), I get all 0s. Are you sure that this code that reads them is correct? I don't see why they should be all 0s if you have not explicitly cleared them yourself. The SEXIT instruction does not do anything to the PMRs. > I have been assuming that "do not match" means "were not different when > they were last used." Is it the case that I must re-enable Protected > Memory before invoking SENTER again? Something else? Can you try disabling the PMRs between calls to SENTER and see if that fixes it? Joe > > Thanks, > -Jon > > > > *** big debug output follows *** > > (XEN) JON: dump_iommu_info() > (XEN) > (XEN) iommu 0: nr_pt_levels = 3. > (XEN) Queued Invalidation: not supported. > (XEN) Interrupt Remapping: not supported. > (XEN) ---- print_iommu_regs ---- > (XEN) print_iommu_regs: drhd->address = fed92000 > (XEN) print_iommu_regs: DMAR_VER_REG = 10 > (XEN) print_iommu_regs: DMAR_CAP_REG = c0000020230270 > (XEN) print_iommu_regs: n_fault_reg = 1 > (XEN) print_iommu_regs: fault_recording_offset_l = 200 > (XEN) print_iommu_regs: fault_recording_offset_h = 208 > (XEN) print_iommu_regs: fault_recording_reg_l = 0 > (XEN) print_iommu_regs: fault_recording_reg_h = 0 > (XEN) print_iommu_regs: DMAR_ECAP_REG = 1000 > (XEN) print_iommu_regs: DMAR_GCMD_REG = 0 > (XEN) print_iommu_regs: DMAR_GSTS_REG = 40000000 > (XEN) print_iommu_regs: DMAR_RTADDR_REG = 7c7bf000 > (XEN) print_iommu_regs: DMAR_CCMD_REG = 800000000000000 > (XEN) print_iommu_regs: DMAR_FSTS_REG = 0 > (XEN) print_iommu_regs: DMAR_FECTL_REG = 0 > (XEN) print_iommu_regs: DMAR_FEDATA_REG = 4090 > (XEN) print_iommu_regs: DMAR_FEADDR_REG = fee00000 > (XEN) print_iommu_regs: DMAR_FEUADDR_REG = 0 > (XEN) print_iommu_regs: DMAR_PMEN_REG = 0 > (XEN) print_iommu_regs: DMAR_PLMBASE_REG = 0 > (XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 0 > (XEN) print_iommu_regs: DMAR_PHMBASE_REG = 0 > (XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0 > (XEN) > (XEN) iommu 1: nr_pt_levels = 3. > (XEN) Queued Invalidation: not supported. > (XEN) Interrupt Remapping: not supported. > (XEN) ---- print_iommu_regs ---- > (XEN) print_iommu_regs: drhd->address = fed91000 > (XEN) print_iommu_regs: DMAR_VER_REG = 10 > (XEN) print_iommu_regs: DMAR_CAP_REG = c0000020230270 > (XEN) print_iommu_regs: n_fault_reg = 1 > (XEN) print_iommu_regs: fault_recording_offset_l = 200 > (XEN) print_iommu_regs: fault_recording_offset_h = 208 > (XEN) print_iommu_regs: fault_recording_reg_l = 0 > (XEN) print_iommu_regs: fault_recording_reg_h = 10 > (XEN) print_iommu_regs: DMAR_ECAP_REG = 1000 > (XEN) print_iommu_regs: DMAR_GCMD_REG = 0 > (XEN) print_iommu_regs: DMAR_GSTS_REG = 40000000 > (XEN) print_iommu_regs: DMAR_RTADDR_REG = 7c7be000 > (XEN) print_iommu_regs: DMAR_CCMD_REG = 800000000000000 > (XEN) print_iommu_regs: DMAR_FSTS_REG = 0 > (XEN) print_iommu_regs: DMAR_FECTL_REG = 0 > (XEN) print_iommu_regs: DMAR_FEDATA_REG = 4098 > (XEN) print_iommu_regs: DMAR_FEADDR_REG = fee00000 > (XEN) print_iommu_regs: DMAR_FEUADDR_REG = 0 > (XEN) print_iommu_regs: DMAR_PMEN_REG = 80000001 > (XEN) print_iommu_regs: DMAR_PLMBASE_REG = 1000000 > (XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 1000000 > (XEN) print_iommu_regs: DMAR_PHMBASE_REG = 200000 > (XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0 > (XEN) > (XEN) iommu 2: nr_pt_levels = 3. > (XEN) Queued Invalidation: not supported. > (XEN) Interrupt Remapping: not supported. > (XEN) ---- print_iommu_regs ---- > (XEN) print_iommu_regs: drhd->address = fed90000 > (XEN) print_iommu_regs: DMAR_VER_REG = 10 > (XEN) print_iommu_regs: DMAR_CAP_REG = c9008020a30270 > (XEN) print_iommu_regs: n_fault_reg = 1 > (XEN) print_iommu_regs: fault_recording_offset_l = 200 > (XEN) print_iommu_regs: fault_recording_offset_h = 208 > (XEN) print_iommu_regs: fault_recording_reg_l = 0 > (XEN) print_iommu_regs: fault_recording_reg_h = 0 > (XEN) print_iommu_regs: DMAR_ECAP_REG = 1000 > (XEN) print_iommu_regs: DMAR_GCMD_REG = 0 > (XEN) print_iommu_regs: DMAR_GSTS_REG = 40000000 > (XEN) print_iommu_regs: DMAR_RTADDR_REG = 7c7bd000 > (XEN) print_iommu_regs: DMAR_CCMD_REG = 0 > (XEN) print_iommu_regs: DMAR_FSTS_REG = 0 > (XEN) print_iommu_regs: DMAR_FECTL_REG = 0 > (XEN) print_iommu_regs: DMAR_FEDATA_REG = 40a0 > (XEN) print_iommu_regs: DMAR_FEADDR_REG = fee00000 > (XEN) print_iommu_regs: DMAR_FEUADDR_REG = 0 > (XEN) print_iommu_regs: DMAR_PMEN_REG = 0 > (XEN) print_iommu_regs: DMAR_PLMBASE_REG = 0 > (XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 0 > (XEN) print_iommu_regs: DMAR_PHMBASE_REG = 0 > (XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0 > (XEN) > (XEN) iommu 3: nr_pt_levels = 3. > (XEN) Queued Invalidation: not supported. > (XEN) Interrupt Remapping: not supported. > (XEN) ---- print_iommu_regs ---- > (XEN) print_iommu_regs: drhd->address = fed93000 > (XEN) print_iommu_regs: DMAR_VER_REG = 10 > (XEN) print_iommu_regs: DMAR_CAP_REG = c9008020230270 > (XEN) print_iommu_regs: n_fault_reg = 1 > (XEN) print_iommu_regs: fault_recording_offset_l = 200 > (XEN) print_iommu_regs: fault_recording_offset_h = 208 > (XEN) print_iommu_regs: fault_recording_reg_l = 0 > (XEN) print_iommu_regs: fault_recording_reg_h = 0 > (XEN) print_iommu_regs: DMAR_ECAP_REG = 1000 > (XEN) print_iommu_regs: DMAR_GCMD_REG = 0 > (XEN) print_iommu_regs: DMAR_GSTS_REG = 40000000 > (XEN) print_iommu_regs: DMAR_RTADDR_REG = 7c7bc000 > (XEN) print_iommu_regs: DMAR_CCMD_REG = 0 > (XEN) print_iommu_regs: DMAR_FSTS_REG = 0 > (XEN) print_iommu_regs: DMAR_FECTL_REG = 0 > (XEN) print_iommu_regs: DMAR_FEDATA_REG = 40a8 > (XEN) print_iommu_regs: DMAR_FEADDR_REG = fee00000 > (XEN) print_iommu_regs: DMAR_FEUADDR_REG = 0 > (XEN) print_iommu_regs: DMAR_PMEN_REG = 0 > (XEN) print_iommu_regs: DMAR_PLMBASE_REG = 0 > (XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 0 > (XEN) print_iommu_regs: DMAR_PHMBASE_REG = 0 > (XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0 > (XEN) I/O virtualisation enabled > (XEN) I/O virtualisation for PV guests disabled > (XEN) JON: disable_pmr invoked > (XEN) JON: disable_pmr invoked > (XEN) JON: disable_pmr invoked > (XEN) JON: disable_pmr invoked > (XEN) *** LOADING DOMAIN 0 *** > > > > (XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switch > input > to DOM0) > (XEN) > (XEN) iommu 0: nr_pt_levels = 3. > (XEN) Queued Invalidation: not supported. > (XEN) Interrupt Remapping: not supported. > (XEN) ---- print_iommu_regs ---- > (XEN) print_iommu_regs: drhd->address = fed92000 > (XEN) print_iommu_regs: DMAR_VER_REG = 10 > (XEN) print_iommu_regs: DMAR_CAP_REG = c0000020230270 > (XEN) print_iommu_regs: n_fault_reg = 1 > (XEN) print_iommu_regs: fault_recording_offset_l = 200 > (XEN) print_iommu_regs: fault_recording_offset_h = 208 > (XEN) print_iommu_regs: fault_recording_reg_l = 0 > (XEN) print_iommu_regs: fault_recording_reg_h = 0 > (XEN) print_iommu_regs: DMAR_ECAP_REG = 1000 > (XEN) print_iommu_regs: DMAR_GCMD_REG = 80000000 > (XEN) print_iommu_regs: DMAR_GSTS_REG = c0000000 > (XEN) print_iommu_regs: DMAR_RTADDR_REG = 7c7bf000 > (XEN) print_iommu_regs: DMAR_CCMD_REG = 4800000000000000 > (XEN) print_iommu_regs: DMAR_FSTS_REG = 0 > (XEN) print_iommu_regs: DMAR_FECTL_REG = 0 > (XEN) print_iommu_regs: DMAR_FEDATA_REG = 4090 > (XEN) print_iommu_regs: DMAR_FEADDR_REG = fee00000 > (XEN) print_iommu_regs: DMAR_FEUADDR_REG = 0 > (XEN) print_iommu_regs: DMAR_PMEN_REG = 0 > (XEN) print_iommu_regs: DMAR_PLMBASE_REG = 0 > (XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 0 > (XEN) print_iommu_regs: DMAR_PHMBASE_REG = 0 > (XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0 > (XEN) > (XEN) iommu 1: nr_pt_levels = 3. > (XEN) Queued Invalidation: not supported. > (XEN) Interrupt Remapping: not supported. > (XEN) ---- print_iommu_regs ---- > (XEN) print_iommu_regs: drhd->address = fed91000 > (XEN) print_iommu_regs: DMAR_VER_REG = 10 > (XEN) print_iommu_regs: DMAR_CAP_REG = c0000020230270 > (XEN) print_iommu_regs: n_fault_reg = 1 > (XEN) print_iommu_regs: fault_recording_offset_l = 200 > (XEN) print_iommu_regs: fault_recording_offset_h = 208 > (XEN) print_iommu_regs: fault_recording_reg_l = 0 > (XEN) print_iommu_regs: fault_recording_reg_h = 10 > (XEN) print_iommu_regs: DMAR_ECAP_REG = 1000 > (XEN) print_iommu_regs: DMAR_GCMD_REG = 80000000 > (XEN) print_iommu_regs: DMAR_GSTS_REG = c0000000 > (XEN) print_iommu_regs: DMAR_RTADDR_REG = 7c7be000 > (XEN) print_iommu_regs: DMAR_CCMD_REG = 2800000000000000 > (XEN) print_iommu_regs: DMAR_FSTS_REG = 0 > (XEN) print_iommu_regs: DMAR_FECTL_REG = 0 > (XEN) print_iommu_regs: DMAR_FEDATA_REG = 4098 > (XEN) print_iommu_regs: DMAR_FEADDR_REG = fee00000 > (XEN) print_iommu_regs: DMAR_FEUADDR_REG = 0 > (XEN) print_iommu_regs: DMAR_PMEN_REG = 0 > (XEN) print_iommu_regs: DMAR_PLMBASE_REG = 1000000 > (XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 1000000 > (XEN) print_iommu_regs: DMAR_PHMBASE_REG = 200000 > (XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0 > (XEN) > (XEN) iommu 2: nr_pt_levels = 3. > (XEN) Queued Invalidation: not supported. > (XEN) Interrupt Remapping: not supported. > (XEN) ---- print_iommu_regs ---- > (XEN) print_iommu_regs: drhd->address = fed90000 > (XEN) print_iommu_regs: DMAR_VER_REG = 10 > (XEN) print_iommu_regs: DMAR_CAP_REG = c9008020a30270 > (XEN) print_iommu_regs: n_fault_reg = 1 > (XEN) print_iommu_regs: fault_recording_offset_l = 200 > (XEN) print_iommu_regs: fault_recording_offset_h = 208 > (XEN) print_iommu_regs: fault_recording_reg_l = 0 > (XEN) print_iommu_regs: fault_recording_reg_h = 0 > (XEN) print_iommu_regs: DMAR_ECAP_REG = 1000 > (XEN) print_iommu_regs: DMAR_GCMD_REG = 80000000 > (XEN) print_iommu_regs: DMAR_GSTS_REG = c0000000 > (XEN) print_iommu_regs: DMAR_RTADDR_REG = 7c7bd000 > (XEN) print_iommu_regs: DMAR_CCMD_REG = 4800000000000001 > (XEN) print_iommu_regs: DMAR_FSTS_REG = 0 > (XEN) print_iommu_regs: DMAR_FECTL_REG = 0 > (XEN) print_iommu_regs: DMAR_FEDATA_REG = 40a0 > (XEN) print_iommu_regs: DMAR_FEADDR_REG = fee00000 > (XEN) print_iommu_regs: DMAR_FEUADDR_REG = 0 > (XEN) print_iommu_regs: DMAR_PMEN_REG = 0 > (XEN) print_iommu_regs: DMAR_PLMBASE_REG = 0 > (XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 0 > (XEN) print_iommu_regs: DMAR_PHMBASE_REG = 0 > (XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0 > (XEN) > (XEN) iommu 3: nr_pt_levels = 3. > (XEN) Queued Invalidation: not supported. > (XEN) Interrupt Remapping: not supported. > (XEN) ---- print_iommu_regs ---- > (XEN) print_iommu_regs: drhd->address = fed93000 > (XEN) print_iommu_regs: DMAR_VER_REG = 10 > (XEN) print_iommu_regs: DMAR_CAP_REG = c9008020230270 > (XEN) print_iommu_regs: n_fault_reg = 1 > (XEN) print_iommu_regs: fault_recording_offset_l = 200 > (XEN) print_iommu_regs: fault_recording_offset_h = 208 > (XEN) print_iommu_regs: fault_recording_reg_l = 0 > (XEN) print_iommu_regs: fault_recording_reg_h = 0 > (XEN) print_iommu_regs: DMAR_ECAP_REG = 1000 > (XEN) print_iommu_regs: DMAR_GCMD_REG = 80000000 > (XEN) print_iommu_regs: DMAR_GSTS_REG = c0000000 > (XEN) print_iommu_regs: DMAR_RTADDR_REG = 7c7bc000 > (XEN) print_iommu_regs: DMAR_CCMD_REG = 5000000000000001 > (XEN) print_iommu_regs: DMAR_FSTS_REG = 0 > (XEN) print_iommu_regs: DMAR_FECTL_REG = 0 > (XEN) print_iommu_regs: DMAR_FEDATA_REG = 40a8 > (XEN) print_iommu_regs: DMAR_FEADDR_REG = fee00000 > (XEN) print_iommu_regs: DMAR_FEUADDR_REG = 0 > (XEN) print_iommu_regs: DMAR_PMEN_REG = 0 > (XEN) print_iommu_regs: DMAR_PLMBASE_REG = 0 > (XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 0 > (XEN) print_iommu_regs: DMAR_PHMBASE_REG = 0 > (XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0 > > > > Cihula, Joseph wrote: > >> From: Jonathan M. McCune [mailto:jon...@cm...] > >> Sent: Friday, October 10, 2008 3:11 PM > >> > >> Hi Joe, list, > >> > >> I started digging through this. > >> > >> In the VT-d spec, the very beginning of chapter 7 says that each DMA > >> remapping hardware unit is placed at a system-specific 4K-aligned > >> memory mapped address, and that the BIOS will report where these > are. > >> > >> I realized I don't know what these addresses are, and Ch. 5 told me > to > >> look at the DMAR table. > >> > >> I wrote some code to decode the DMAR table, and the subsequent DRHD > / > >> RMRR entries it contains, and the subsequent Device Scope Structures > >> that they contain. > >> > >> When run on my system following execution of SENTER, the big long > >> printout at the end of this email ensues. I made an educated guess > >> that the DRHD structure with flags = 1 (see Table 5-3 in the VT-d > > spec) > >> might be the DMA remapping hardware unit??? of choice. I tried to > > print its > >> values at the relevant offsets for the PMRs (see Table 7-2), but I > get > >> all 0s: > >> > >> TBOOT: ACPI VT-d DRHD structure @ 7c6a3e78: > >> TBOOT: Type: 0 > >> TBOOT: Length: 0x10 (16) > >> TBOOT: Flags: 1 > >> TBOOT: Register Base Address: 0xfed93000 > >> TBOOT: DMAR DRHD Registers @ fed93000: > >> TBOOT: PMR Enable: 0x0 > >> TBOOT: PMR Low Base: 0x0 > >> TBOOT: PMR Low Limit: 0x0 > >> TBOOT: PMR High Base: 0x0 > >> TBOOT: PMR High Limit: 0x0 > >> > >> > >> Am I on the right track here? How do I know which of these "DMA > >> remapping hardware units" is the right one? > > > > These entries are not 4k aligned, so they aren't the right places. > The > > easiest thing to do is to look at the Xen code that parses the tables > > and reads the registers to see how to do it. > > > >> Thanks! > >> -Jon > >> > >> > >> > >> > >> > >> TBOOT: acpi_dmar = 7c6a3df0 > >> TBOOT: VT-d DMAR @ 7c6a3df0 (len 360 bytes): > >> 44 4d 41 52 68 01 00 00 01 c7 31 30 31 36 30 37 > >> 4f 45 4d 44 4d 41 52 20 01 00 00 00 4d 53 46 54 > >> 97 00 00 00 23 00 00 00 00 00 00 00 00 00 00 00 > >> 00 00 18 00 00 00 00 00 00 00 d9 fe 00 00 00 00 > >> 01 08 00 00 00 00 1b 00 00 00 18 00 00 00 00 00 > >> 00 10 d9 fe 00 00 00 00 01 08 00 00 00 00 02 00 > >> 00 00 28 00 00 00 00 00 00 20 d9 fe 00 00 00 00 > >> 01 08 00 00 00 00 03 00 01 08 00 00 00 00 03 02 > >> 01 08 00 00 00 00 03 03 00 00 10 00 01 00 00 00 > >> 00 30 d9 fe 00 00 00 00 01 00 58 00 00 00 00 00 > >> 00 d0 0e 00 00 00 00 00 ff ff 0e 00 00 00 00 00 > >> 01 08 00 00 00 00 1d 00 01 08 00 00 00 00 1d 01 > >> 01 08 00 00 00 00 1d 02 01 08 00 00 00 00 1d 07 > >> 01 08 00 00 00 00 1a 00 01 08 00 00 00 00 1a 01 > >> 01 08 00 00 00 00 1a 02 01 08 00 00 00 00 1a 07 > >> 01 00 58 00 00 00 00 00 00 00 2f 7d 00 00 00 00 > >> ff ff 2f 7d 00 00 00 00 01 08 00 00 00 00 1d 00 > >> 01 08 00 00 00 00 1d 01 01 08 00 00 00 00 1d 02 > >> 01 08 00 00 00 00 1d 07 01 08 00 00 00 00 1a 00 > >> 01 08 00 00 00 00 1a 01 01 08 00 00 00 00 1a 02 > >> 01 08 00 00 00 00 1a 07 01 00 20 00 00 00 00 00 > >> 00 00 60 7d 00 00 00 00 ff ff ff 7d 00 00 00 00 > >> 01 08 00 00 00 00 02 00 > >> TBOOT: ACPI VT-d DMAR table @ 7c6a3df0 (len 48 bytes): > >> TBOOT: Signature: DMAR > >> TBOOT: Length: 0x168 (360) > >> TBOOT: Revision: 1 > >> TBOOT: Checksum: c7 > >> TBOOT: OEMID: 101607 > >> TBOOT: OEM Table ID: OEMDMAR > >> TBOOT: OEM Revision: 1 > >> TBOOT: Creator ID: MSFT > >> TBOOT: Creator Revision: 0x97 > >> TBOOT: Host Address Width: 0x23 (35) > >> TBOOT: ACPI VT-d DRHD structure @ 7c6a3e20: > >> TBOOT: Type: 0 > >> TBOOT: Length: 0x18 (24) > >> TBOOT: Flags: 0 > >> TBOOT: Register Base Address: 0xfed90000 > >> TBOOT: Device Scope entry @ 7c6a3e30: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 1b 00 > >> > >> TBOOT: ACPI VT-d DRHD structure @ 7c6a3e38: > >> TBOOT: Type: 0 > >> TBOOT: Length: 0x18 (24) > >> TBOOT: Flags: 0 > >> TBOOT: Register Base Address: 0xfed91000 > >> TBOOT: Device Scope entry @ 7c6a3e48: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 02 00 > >> > >> TBOOT: ACPI VT-d DRHD structure @ 7c6a3e50: > >> TBOOT: Type: 0 > >> TBOOT: Length: 0x28 (40) > >> TBOOT: Flags: 0 > >> TBOOT: Register Base Address: 0xfed92000 > >> TBOOT: Device Scope entry @ 7c6a3e60: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 03 00 > >> > >> TBOOT: Device Scope entry @ 7c6a3e68: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 03 02 > >> > >> TBOOT: Device Scope entry @ 7c6a3e70: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 03 03 > >> > >> TBOOT: ACPI VT-d DRHD structure @ 7c6a3e78: > >> TBOOT: Type: 0 > >> TBOOT: Length: 0x10 (16) > >> TBOOT: Flags: 1 > >> TBOOT: Register Base Address: 0xfed93000 > >> TBOOT: DMAR DRHD Registers @ fed93000: > >> TBOOT: PMR Enable: 0x0 > >> TBOOT: PMR Low Base: 0x0 > >> TBOOT: PMR Low Limit: 0x0 > >> TBOOT: PMR High Base: 0x0 > >> TBOOT: PMR High Limit: 0x0 > >> TBOOT: ACPI VT-d RMRR structure @ 7c6a3e88: > >> TBOOT: Type: 0x1 (1) > >> TBOOT: Length: 0x58 (88) > >> TBOOT: Flag: 0x0 > >> TBOOT: RMR Base Address: ed000 > >> TBOOT: RMR Limit Address: effff > >> TBOOT: Device Scope entry @ 7c6a3ea0: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 1d 00 > >> > >> TBOOT: Device Scope entry @ 7c6a3ea8: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 1d 01 > >> > >> TBOOT: Device Scope entry @ 7c6a3eb0: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 1d 02 > >> > >> TBOOT: Device Scope entry @ 7c6a3eb8: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 1d 07 > >> > >> TBOOT: Device Scope entry @ 7c6a3ec0: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 1a 00 > >> > >> TBOOT: Device Scope entry @ 7c6a3ec8: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 1a 01 > >> > >> TBOOT: Device Scope entry @ 7c6a3ed0: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 1a 02 > >> > >> TBOOT: Device Scope entry @ 7c6a3ed8: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 1a 07 > >> > >> TBOOT: ACPI VT-d RMRR structure @ 7c6a3ee0: > >> TBOOT: Type: 0x1 (1) > >> TBOOT: Length: 0x58 (88) > >> TBOOT: Flag: 0x0 > >> TBOOT: RMR Base Address: 7d2f0000 > >> TBOOT: RMR Limit Address: 7d2fffff > >> TBOOT: Device Scope entry @ 7c6a3ef8: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 1d 00 > >> > >> TBOOT: Device Scope entry @ 7c6a3f00: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 1d 01 > >> > >> TBOOT: Device Scope entry @ 7c6a3f08: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 1d 02 > >> > >> TBOOT: Device Scope entry @ 7c6a3f10: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 1d 07 > >> > >> TBOOT: Device Scope entry @ 7c6a3f18: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 1a 00 > >> > >> TBOOT: Device Scope entry @ 7c6a3f20: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 1a 01 > >> > >> TBOOT: Device Scope entry @ 7c6a3f28: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 1a 02 > >> > >> TBOOT: Device Scope entry @ 7c6a3f30: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 1a 07 > >> > >> TBOOT: ACPI VT-d RMRR structure @ 7c6a3f38: > >> TBOOT: Type: 0x1 (1) > >> TBOOT: Length: 0x20 (32) > >> TBOOT: Flag: 0x0 > >> TBOOT: RMR Base Address: 7d600000 > >> TBOOT: RMR Limit Address: 7dffffff > >> TBOOT: Device Scope entry @ 7c6a3f50: > >> TBOOT: Type: 0x1 > >> TBOOT: Length: 0x8 > >> TBOOT: Segment Number: 0x0 > >> TBOOT: Starting Bus Number: 0x0 > >> TBOOT: Raw PCI Path (Length - 4): 00 00 02 00 > >> > >> TBOOT: VT-d DMAR table OK > >> > >> > >> Cihula, Joseph wrote: > >>>> From: Jonathan M. McCune [mailto:jon...@cm...] > >>>> Sent: Thursday, October 09, 2008 10:27 AM > >>>> > >>>> Hi Joe, > >>>> > >>>> Cihula, Joseph wrote: > >>>>> It is really: > >>>>> Current values of VT-d PMR registers do not match requested > >>>>> values in SinitMleData > >>>>> > >>>>> which means that some code has already programmed the PMRs but > not > >>> to > >>>>> the same values that the MLE is requesting. Because the PMRs > >> cannot > >>>> be > >>>>> changed reliably once they are set/enabled, this is not an > allowed > >>>>> condition. > >>>> I am successfully invoking SENTER / SEXIT and then returning > > control > >>> to > >>>> the legacy OS once per boot cycle. When I try to execute SENTER a > >>>> second time, the system reboots and LT.ERRORCODE is populated with > >> the > >>>> above error. However, I cannot figure out what is wrong with my > > PMR > >>>> values. > >>>> > >>>> Is there a way to read the current values, so that I can see how > >> they > >>>> are set following the first SENTER? Looking through the MLE manual > >> and > >>>> the Sw Dev Manual Vol 2b has left me without much insight. > >>> VT-d registers are described in the VT-d spec at: > >>> > > > http://download.intel.com/technology/computing/vptech/Intel(r)_VT_for_D > >> i > >>> rect_IO.pdf > >>> > >>>> My MLE resides at physical address 0x00c00000 and consumes less > > than > >>>> 0x200000 (2MB) bytes. > >>>> > >>>> TBOOT: vtd_pmr_lo_base: 0xc00000 > >>>> TBOOT: vtd_pmr_lo_size: 0x200000 > >>>> TBOOT: vtd_pmr_hi_base: 0x0 > >>>> TBOOT: vtd_pmr_hi_size: 0x0 > >>>> > >>>> I'm fairly confident that the os_sinit_data_t.vtd_pmr_* values are > >>>> being > >>>> set identically prior to both invocations of SENTER (when I print > >> them > >>>> out, the above is what I see). > >>> If you could use the VT-d spec to read and output the PMRs before > >>> launch, that should determine if they are somehow getting changed > >>> between invocations. > >>> > >>>> Thanks, > >>>> -Jon > > |
|
From: Jonathan M. M. <jon...@cm...> - 2008-10-14 22:22:21
|
Hi Joe, list,
I'm able to read the registers now, but I'm still not sure what I'm
doing wrong. Details...
With the latest xen-unstable.hg and tboot.hg, I added some code to
xen/drivers/passthrough/vtd/utils.c:dump_iommu_info() to also dump the
Protected Memory Registers (enable, low base/limit, high base/limit). I
inserted a call so that these registers get printed before more
sophisticated remapping is enabled. I then printed them again manually
after Xen has fully booted (using 3xCtrl+A, V).
The 0xfed93000 from my previous email was 4K aligned, but it turns out
that the only DRHD with non-zero PMR registers on my system is
0xfed91000 (low base of 16MB, size 16MB), and only during boot time
(this makes sense, since disable_pmr() is called for each DRHD):
(XEN) print_iommu_regs: DMAR_PMEN_REG = 80000001
(XEN) print_iommu_regs: DMAR_PLMBASE_REG = 1000000
(XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 1000000
(XEN) print_iommu_regs: DMAR_PHMBASE_REG = 200000
(XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0
When I invoke SENTER with my code (on a non-Xen, vanilla Linux system),
I configure the low PMR region to be 2 MB in size, starting at 12 MB of
physical memory (kmalloc()'d).
TBOOT: os_sinit_data->vtd_pmr_lo_base: 0xc00000
TBOOT: os_sinit_data->vtd_pmr_lo_size: 0x200000
TBOOT: os_sinit_data->vtd_pmr_hi_base: 0x0
TBOOT: os_sinit_data->vtd_pmr_hi_size: 0x0
It uses these same memory regions every time, and reliably works once
but then fails (triggering a reboot) with:
TBOOT: LT.ERRORCODE=c00038f1
TBOOT: AC module error : acm_type=1, progress=0f, error=e
1110 Current values of VT-d PMR registers do not match
requested values in SinitMleData
If I try to read the PMR registers between sessions (i.e., while the
system is _not_ in any kind of secure mode; SEXIT _did_ execute
following SENTER), I get all 0s.
I have been assuming that "do not match" means "were not different when
they were last used." Is it the case that I must re-enable Protected
Memory before invoking SENTER again? Something else?
Thanks,
-Jon
*** big debug output follows ***
(XEN) JON: dump_iommu_info()
(XEN)
(XEN) iommu 0: nr_pt_levels = 3.
(XEN) Queued Invalidation: not supported.
(XEN) Interrupt Remapping: not supported.
(XEN) ---- print_iommu_regs ----
(XEN) print_iommu_regs: drhd->address = fed92000
(XEN) print_iommu_regs: DMAR_VER_REG = 10
(XEN) print_iommu_regs: DMAR_CAP_REG = c0000020230270
(XEN) print_iommu_regs: n_fault_reg = 1
(XEN) print_iommu_regs: fault_recording_offset_l = 200
(XEN) print_iommu_regs: fault_recording_offset_h = 208
(XEN) print_iommu_regs: fault_recording_reg_l = 0
(XEN) print_iommu_regs: fault_recording_reg_h = 0
(XEN) print_iommu_regs: DMAR_ECAP_REG = 1000
(XEN) print_iommu_regs: DMAR_GCMD_REG = 0
(XEN) print_iommu_regs: DMAR_GSTS_REG = 40000000
(XEN) print_iommu_regs: DMAR_RTADDR_REG = 7c7bf000
(XEN) print_iommu_regs: DMAR_CCMD_REG = 800000000000000
(XEN) print_iommu_regs: DMAR_FSTS_REG = 0
(XEN) print_iommu_regs: DMAR_FECTL_REG = 0
(XEN) print_iommu_regs: DMAR_FEDATA_REG = 4090
(XEN) print_iommu_regs: DMAR_FEADDR_REG = fee00000
(XEN) print_iommu_regs: DMAR_FEUADDR_REG = 0
(XEN) print_iommu_regs: DMAR_PMEN_REG = 0
(XEN) print_iommu_regs: DMAR_PLMBASE_REG = 0
(XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 0
(XEN) print_iommu_regs: DMAR_PHMBASE_REG = 0
(XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0
(XEN)
(XEN) iommu 1: nr_pt_levels = 3.
(XEN) Queued Invalidation: not supported.
(XEN) Interrupt Remapping: not supported.
(XEN) ---- print_iommu_regs ----
(XEN) print_iommu_regs: drhd->address = fed91000
(XEN) print_iommu_regs: DMAR_VER_REG = 10
(XEN) print_iommu_regs: DMAR_CAP_REG = c0000020230270
(XEN) print_iommu_regs: n_fault_reg = 1
(XEN) print_iommu_regs: fault_recording_offset_l = 200
(XEN) print_iommu_regs: fault_recording_offset_h = 208
(XEN) print_iommu_regs: fault_recording_reg_l = 0
(XEN) print_iommu_regs: fault_recording_reg_h = 10
(XEN) print_iommu_regs: DMAR_ECAP_REG = 1000
(XEN) print_iommu_regs: DMAR_GCMD_REG = 0
(XEN) print_iommu_regs: DMAR_GSTS_REG = 40000000
(XEN) print_iommu_regs: DMAR_RTADDR_REG = 7c7be000
(XEN) print_iommu_regs: DMAR_CCMD_REG = 800000000000000
(XEN) print_iommu_regs: DMAR_FSTS_REG = 0
(XEN) print_iommu_regs: DMAR_FECTL_REG = 0
(XEN) print_iommu_regs: DMAR_FEDATA_REG = 4098
(XEN) print_iommu_regs: DMAR_FEADDR_REG = fee00000
(XEN) print_iommu_regs: DMAR_FEUADDR_REG = 0
(XEN) print_iommu_regs: DMAR_PMEN_REG = 80000001
(XEN) print_iommu_regs: DMAR_PLMBASE_REG = 1000000
(XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 1000000
(XEN) print_iommu_regs: DMAR_PHMBASE_REG = 200000
(XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0
(XEN)
(XEN) iommu 2: nr_pt_levels = 3.
(XEN) Queued Invalidation: not supported.
(XEN) Interrupt Remapping: not supported.
(XEN) ---- print_iommu_regs ----
(XEN) print_iommu_regs: drhd->address = fed90000
(XEN) print_iommu_regs: DMAR_VER_REG = 10
(XEN) print_iommu_regs: DMAR_CAP_REG = c9008020a30270
(XEN) print_iommu_regs: n_fault_reg = 1
(XEN) print_iommu_regs: fault_recording_offset_l = 200
(XEN) print_iommu_regs: fault_recording_offset_h = 208
(XEN) print_iommu_regs: fault_recording_reg_l = 0
(XEN) print_iommu_regs: fault_recording_reg_h = 0
(XEN) print_iommu_regs: DMAR_ECAP_REG = 1000
(XEN) print_iommu_regs: DMAR_GCMD_REG = 0
(XEN) print_iommu_regs: DMAR_GSTS_REG = 40000000
(XEN) print_iommu_regs: DMAR_RTADDR_REG = 7c7bd000
(XEN) print_iommu_regs: DMAR_CCMD_REG = 0
(XEN) print_iommu_regs: DMAR_FSTS_REG = 0
(XEN) print_iommu_regs: DMAR_FECTL_REG = 0
(XEN) print_iommu_regs: DMAR_FEDATA_REG = 40a0
(XEN) print_iommu_regs: DMAR_FEADDR_REG = fee00000
(XEN) print_iommu_regs: DMAR_FEUADDR_REG = 0
(XEN) print_iommu_regs: DMAR_PMEN_REG = 0
(XEN) print_iommu_regs: DMAR_PLMBASE_REG = 0
(XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 0
(XEN) print_iommu_regs: DMAR_PHMBASE_REG = 0
(XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0
(XEN)
(XEN) iommu 3: nr_pt_levels = 3.
(XEN) Queued Invalidation: not supported.
(XEN) Interrupt Remapping: not supported.
(XEN) ---- print_iommu_regs ----
(XEN) print_iommu_regs: drhd->address = fed93000
(XEN) print_iommu_regs: DMAR_VER_REG = 10
(XEN) print_iommu_regs: DMAR_CAP_REG = c9008020230270
(XEN) print_iommu_regs: n_fault_reg = 1
(XEN) print_iommu_regs: fault_recording_offset_l = 200
(XEN) print_iommu_regs: fault_recording_offset_h = 208
(XEN) print_iommu_regs: fault_recording_reg_l = 0
(XEN) print_iommu_regs: fault_recording_reg_h = 0
(XEN) print_iommu_regs: DMAR_ECAP_REG = 1000
(XEN) print_iommu_regs: DMAR_GCMD_REG = 0
(XEN) print_iommu_regs: DMAR_GSTS_REG = 40000000
(XEN) print_iommu_regs: DMAR_RTADDR_REG = 7c7bc000
(XEN) print_iommu_regs: DMAR_CCMD_REG = 0
(XEN) print_iommu_regs: DMAR_FSTS_REG = 0
(XEN) print_iommu_regs: DMAR_FECTL_REG = 0
(XEN) print_iommu_regs: DMAR_FEDATA_REG = 40a8
(XEN) print_iommu_regs: DMAR_FEADDR_REG = fee00000
(XEN) print_iommu_regs: DMAR_FEUADDR_REG = 0
(XEN) print_iommu_regs: DMAR_PMEN_REG = 0
(XEN) print_iommu_regs: DMAR_PLMBASE_REG = 0
(XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 0
(XEN) print_iommu_regs: DMAR_PHMBASE_REG = 0
(XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled
(XEN) JON: disable_pmr invoked
(XEN) JON: disable_pmr invoked
(XEN) JON: disable_pmr invoked
(XEN) JON: disable_pmr invoked
(XEN) *** LOADING DOMAIN 0 ***
(XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switch input
to DOM0)
(XEN)
(XEN) iommu 0: nr_pt_levels = 3.
(XEN) Queued Invalidation: not supported.
(XEN) Interrupt Remapping: not supported.
(XEN) ---- print_iommu_regs ----
(XEN) print_iommu_regs: drhd->address = fed92000
(XEN) print_iommu_regs: DMAR_VER_REG = 10
(XEN) print_iommu_regs: DMAR_CAP_REG = c0000020230270
(XEN) print_iommu_regs: n_fault_reg = 1
(XEN) print_iommu_regs: fault_recording_offset_l = 200
(XEN) print_iommu_regs: fault_recording_offset_h = 208
(XEN) print_iommu_regs: fault_recording_reg_l = 0
(XEN) print_iommu_regs: fault_recording_reg_h = 0
(XEN) print_iommu_regs: DMAR_ECAP_REG = 1000
(XEN) print_iommu_regs: DMAR_GCMD_REG = 80000000
(XEN) print_iommu_regs: DMAR_GSTS_REG = c0000000
(XEN) print_iommu_regs: DMAR_RTADDR_REG = 7c7bf000
(XEN) print_iommu_regs: DMAR_CCMD_REG = 4800000000000000
(XEN) print_iommu_regs: DMAR_FSTS_REG = 0
(XEN) print_iommu_regs: DMAR_FECTL_REG = 0
(XEN) print_iommu_regs: DMAR_FEDATA_REG = 4090
(XEN) print_iommu_regs: DMAR_FEADDR_REG = fee00000
(XEN) print_iommu_regs: DMAR_FEUADDR_REG = 0
(XEN) print_iommu_regs: DMAR_PMEN_REG = 0
(XEN) print_iommu_regs: DMAR_PLMBASE_REG = 0
(XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 0
(XEN) print_iommu_regs: DMAR_PHMBASE_REG = 0
(XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0
(XEN)
(XEN) iommu 1: nr_pt_levels = 3.
(XEN) Queued Invalidation: not supported.
(XEN) Interrupt Remapping: not supported.
(XEN) ---- print_iommu_regs ----
(XEN) print_iommu_regs: drhd->address = fed91000
(XEN) print_iommu_regs: DMAR_VER_REG = 10
(XEN) print_iommu_regs: DMAR_CAP_REG = c0000020230270
(XEN) print_iommu_regs: n_fault_reg = 1
(XEN) print_iommu_regs: fault_recording_offset_l = 200
(XEN) print_iommu_regs: fault_recording_offset_h = 208
(XEN) print_iommu_regs: fault_recording_reg_l = 0
(XEN) print_iommu_regs: fault_recording_reg_h = 10
(XEN) print_iommu_regs: DMAR_ECAP_REG = 1000
(XEN) print_iommu_regs: DMAR_GCMD_REG = 80000000
(XEN) print_iommu_regs: DMAR_GSTS_REG = c0000000
(XEN) print_iommu_regs: DMAR_RTADDR_REG = 7c7be000
(XEN) print_iommu_regs: DMAR_CCMD_REG = 2800000000000000
(XEN) print_iommu_regs: DMAR_FSTS_REG = 0
(XEN) print_iommu_regs: DMAR_FECTL_REG = 0
(XEN) print_iommu_regs: DMAR_FEDATA_REG = 4098
(XEN) print_iommu_regs: DMAR_FEADDR_REG = fee00000
(XEN) print_iommu_regs: DMAR_FEUADDR_REG = 0
(XEN) print_iommu_regs: DMAR_PMEN_REG = 0
(XEN) print_iommu_regs: DMAR_PLMBASE_REG = 1000000
(XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 1000000
(XEN) print_iommu_regs: DMAR_PHMBASE_REG = 200000
(XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0
(XEN)
(XEN) iommu 2: nr_pt_levels = 3.
(XEN) Queued Invalidation: not supported.
(XEN) Interrupt Remapping: not supported.
(XEN) ---- print_iommu_regs ----
(XEN) print_iommu_regs: drhd->address = fed90000
(XEN) print_iommu_regs: DMAR_VER_REG = 10
(XEN) print_iommu_regs: DMAR_CAP_REG = c9008020a30270
(XEN) print_iommu_regs: n_fault_reg = 1
(XEN) print_iommu_regs: fault_recording_offset_l = 200
(XEN) print_iommu_regs: fault_recording_offset_h = 208
(XEN) print_iommu_regs: fault_recording_reg_l = 0
(XEN) print_iommu_regs: fault_recording_reg_h = 0
(XEN) print_iommu_regs: DMAR_ECAP_REG = 1000
(XEN) print_iommu_regs: DMAR_GCMD_REG = 80000000
(XEN) print_iommu_regs: DMAR_GSTS_REG = c0000000
(XEN) print_iommu_regs: DMAR_RTADDR_REG = 7c7bd000
(XEN) print_iommu_regs: DMAR_CCMD_REG = 4800000000000001
(XEN) print_iommu_regs: DMAR_FSTS_REG = 0
(XEN) print_iommu_regs: DMAR_FECTL_REG = 0
(XEN) print_iommu_regs: DMAR_FEDATA_REG = 40a0
(XEN) print_iommu_regs: DMAR_FEADDR_REG = fee00000
(XEN) print_iommu_regs: DMAR_FEUADDR_REG = 0
(XEN) print_iommu_regs: DMAR_PMEN_REG = 0
(XEN) print_iommu_regs: DMAR_PLMBASE_REG = 0
(XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 0
(XEN) print_iommu_regs: DMAR_PHMBASE_REG = 0
(XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0
(XEN)
(XEN) iommu 3: nr_pt_levels = 3.
(XEN) Queued Invalidation: not supported.
(XEN) Interrupt Remapping: not supported.
(XEN) ---- print_iommu_regs ----
(XEN) print_iommu_regs: drhd->address = fed93000
(XEN) print_iommu_regs: DMAR_VER_REG = 10
(XEN) print_iommu_regs: DMAR_CAP_REG = c9008020230270
(XEN) print_iommu_regs: n_fault_reg = 1
(XEN) print_iommu_regs: fault_recording_offset_l = 200
(XEN) print_iommu_regs: fault_recording_offset_h = 208
(XEN) print_iommu_regs: fault_recording_reg_l = 0
(XEN) print_iommu_regs: fault_recording_reg_h = 0
(XEN) print_iommu_regs: DMAR_ECAP_REG = 1000
(XEN) print_iommu_regs: DMAR_GCMD_REG = 80000000
(XEN) print_iommu_regs: DMAR_GSTS_REG = c0000000
(XEN) print_iommu_regs: DMAR_RTADDR_REG = 7c7bc000
(XEN) print_iommu_regs: DMAR_CCMD_REG = 5000000000000001
(XEN) print_iommu_regs: DMAR_FSTS_REG = 0
(XEN) print_iommu_regs: DMAR_FECTL_REG = 0
(XEN) print_iommu_regs: DMAR_FEDATA_REG = 40a8
(XEN) print_iommu_regs: DMAR_FEADDR_REG = fee00000
(XEN) print_iommu_regs: DMAR_FEUADDR_REG = 0
(XEN) print_iommu_regs: DMAR_PMEN_REG = 0
(XEN) print_iommu_regs: DMAR_PLMBASE_REG = 0
(XEN) print_iommu_regs: DMAR_PLMLIMIT_REG = 0
(XEN) print_iommu_regs: DMAR_PHMBASE_REG = 0
(XEN) print_iommu_regs: DMAR_PHMLIMIT_REG = 0
Cihula, Joseph wrote:
>> From: Jonathan M. McCune [mailto:jon...@cm...]
>> Sent: Friday, October 10, 2008 3:11 PM
>>
>> Hi Joe, list,
>>
>> I started digging through this.
>>
>> In the VT-d spec, the very beginning of chapter 7 says that each DMA
>> remapping hardware unit is placed at a system-specific 4K-aligned
>> memory mapped address, and that the BIOS will report where these are.
>>
>> I realized I don't know what these addresses are, and Ch. 5 told me to
>> look at the DMAR table.
>>
>> I wrote some code to decode the DMAR table, and the subsequent DRHD /
>> RMRR entries it contains, and the subsequent Device Scope Structures
>> that they contain.
>>
>> When run on my system following execution of SENTER, the big long
>> printout at the end of this email ensues. I made an educated guess
>> that the DRHD structure with flags = 1 (see Table 5-3 in the VT-d
> spec)
>> might be the DMA remapping hardware unit??? of choice. I tried to
> print its
>> values at the relevant offsets for the PMRs (see Table 7-2), but I get
>> all 0s:
>>
>> TBOOT: ACPI VT-d DRHD structure @ 7c6a3e78:
>> TBOOT: Type: 0
>> TBOOT: Length: 0x10 (16)
>> TBOOT: Flags: 1
>> TBOOT: Register Base Address: 0xfed93000
>> TBOOT: DMAR DRHD Registers @ fed93000:
>> TBOOT: PMR Enable: 0x0
>> TBOOT: PMR Low Base: 0x0
>> TBOOT: PMR Low Limit: 0x0
>> TBOOT: PMR High Base: 0x0
>> TBOOT: PMR High Limit: 0x0
>>
>>
>> Am I on the right track here? How do I know which of these "DMA
>> remapping hardware units" is the right one?
>
> These entries are not 4k aligned, so they aren't the right places. The
> easiest thing to do is to look at the Xen code that parses the tables
> and reads the registers to see how to do it.
>
>> Thanks!
>> -Jon
>>
>>
>>
>>
>>
>> TBOOT: acpi_dmar = 7c6a3df0
>> TBOOT: VT-d DMAR @ 7c6a3df0 (len 360 bytes):
>> 44 4d 41 52 68 01 00 00 01 c7 31 30 31 36 30 37
>> 4f 45 4d 44 4d 41 52 20 01 00 00 00 4d 53 46 54
>> 97 00 00 00 23 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 18 00 00 00 00 00 00 00 d9 fe 00 00 00 00
>> 01 08 00 00 00 00 1b 00 00 00 18 00 00 00 00 00
>> 00 10 d9 fe 00 00 00 00 01 08 00 00 00 00 02 00
>> 00 00 28 00 00 00 00 00 00 20 d9 fe 00 00 00 00
>> 01 08 00 00 00 00 03 00 01 08 00 00 00 00 03 02
>> 01 08 00 00 00 00 03 03 00 00 10 00 01 00 00 00
>> 00 30 d9 fe 00 00 00 00 01 00 58 00 00 00 00 00
>> 00 d0 0e 00 00 00 00 00 ff ff 0e 00 00 00 00 00
>> 01 08 00 00 00 00 1d 00 01 08 00 00 00 00 1d 01
>> 01 08 00 00 00 00 1d 02 01 08 00 00 00 00 1d 07
>> 01 08 00 00 00 00 1a 00 01 08 00 00 00 00 1a 01
>> 01 08 00 00 00 00 1a 02 01 08 00 00 00 00 1a 07
>> 01 00 58 00 00 00 00 00 00 00 2f 7d 00 00 00 00
>> ff ff 2f 7d 00 00 00 00 01 08 00 00 00 00 1d 00
>> 01 08 00 00 00 00 1d 01 01 08 00 00 00 00 1d 02
>> 01 08 00 00 00 00 1d 07 01 08 00 00 00 00 1a 00
>> 01 08 00 00 00 00 1a 01 01 08 00 00 00 00 1a 02
>> 01 08 00 00 00 00 1a 07 01 00 20 00 00 00 00 00
>> 00 00 60 7d 00 00 00 00 ff ff ff 7d 00 00 00 00
>> 01 08 00 00 00 00 02 00
>> TBOOT: ACPI VT-d DMAR table @ 7c6a3df0 (len 48 bytes):
>> TBOOT: Signature: DMAR
>> TBOOT: Length: 0x168 (360)
>> TBOOT: Revision: 1
>> TBOOT: Checksum: c7
>> TBOOT: OEMID: 101607
>> TBOOT: OEM Table ID: OEMDMAR
>> TBOOT: OEM Revision: 1
>> TBOOT: Creator ID: MSFT
>> TBOOT: Creator Revision: 0x97
>> TBOOT: Host Address Width: 0x23 (35)
>> TBOOT: ACPI VT-d DRHD structure @ 7c6a3e20:
>> TBOOT: Type: 0
>> TBOOT: Length: 0x18 (24)
>> TBOOT: Flags: 0
>> TBOOT: Register Base Address: 0xfed90000
>> TBOOT: Device Scope entry @ 7c6a3e30:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 1b 00
>>
>> TBOOT: ACPI VT-d DRHD structure @ 7c6a3e38:
>> TBOOT: Type: 0
>> TBOOT: Length: 0x18 (24)
>> TBOOT: Flags: 0
>> TBOOT: Register Base Address: 0xfed91000
>> TBOOT: Device Scope entry @ 7c6a3e48:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 02 00
>>
>> TBOOT: ACPI VT-d DRHD structure @ 7c6a3e50:
>> TBOOT: Type: 0
>> TBOOT: Length: 0x28 (40)
>> TBOOT: Flags: 0
>> TBOOT: Register Base Address: 0xfed92000
>> TBOOT: Device Scope entry @ 7c6a3e60:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 03 00
>>
>> TBOOT: Device Scope entry @ 7c6a3e68:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 03 02
>>
>> TBOOT: Device Scope entry @ 7c6a3e70:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 03 03
>>
>> TBOOT: ACPI VT-d DRHD structure @ 7c6a3e78:
>> TBOOT: Type: 0
>> TBOOT: Length: 0x10 (16)
>> TBOOT: Flags: 1
>> TBOOT: Register Base Address: 0xfed93000
>> TBOOT: DMAR DRHD Registers @ fed93000:
>> TBOOT: PMR Enable: 0x0
>> TBOOT: PMR Low Base: 0x0
>> TBOOT: PMR Low Limit: 0x0
>> TBOOT: PMR High Base: 0x0
>> TBOOT: PMR High Limit: 0x0
>> TBOOT: ACPI VT-d RMRR structure @ 7c6a3e88:
>> TBOOT: Type: 0x1 (1)
>> TBOOT: Length: 0x58 (88)
>> TBOOT: Flag: 0x0
>> TBOOT: RMR Base Address: ed000
>> TBOOT: RMR Limit Address: effff
>> TBOOT: Device Scope entry @ 7c6a3ea0:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 1d 00
>>
>> TBOOT: Device Scope entry @ 7c6a3ea8:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 1d 01
>>
>> TBOOT: Device Scope entry @ 7c6a3eb0:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 1d 02
>>
>> TBOOT: Device Scope entry @ 7c6a3eb8:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 1d 07
>>
>> TBOOT: Device Scope entry @ 7c6a3ec0:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 1a 00
>>
>> TBOOT: Device Scope entry @ 7c6a3ec8:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 1a 01
>>
>> TBOOT: Device Scope entry @ 7c6a3ed0:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 1a 02
>>
>> TBOOT: Device Scope entry @ 7c6a3ed8:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 1a 07
>>
>> TBOOT: ACPI VT-d RMRR structure @ 7c6a3ee0:
>> TBOOT: Type: 0x1 (1)
>> TBOOT: Length: 0x58 (88)
>> TBOOT: Flag: 0x0
>> TBOOT: RMR Base Address: 7d2f0000
>> TBOOT: RMR Limit Address: 7d2fffff
>> TBOOT: Device Scope entry @ 7c6a3ef8:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 1d 00
>>
>> TBOOT: Device Scope entry @ 7c6a3f00:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 1d 01
>>
>> TBOOT: Device Scope entry @ 7c6a3f08:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 1d 02
>>
>> TBOOT: Device Scope entry @ 7c6a3f10:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 1d 07
>>
>> TBOOT: Device Scope entry @ 7c6a3f18:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 1a 00
>>
>> TBOOT: Device Scope entry @ 7c6a3f20:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 1a 01
>>
>> TBOOT: Device Scope entry @ 7c6a3f28:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 1a 02
>>
>> TBOOT: Device Scope entry @ 7c6a3f30:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 1a 07
>>
>> TBOOT: ACPI VT-d RMRR structure @ 7c6a3f38:
>> TBOOT: Type: 0x1 (1)
>> TBOOT: Length: 0x20 (32)
>> TBOOT: Flag: 0x0
>> TBOOT: RMR Base Address: 7d600000
>> TBOOT: RMR Limit Address: 7dffffff
>> TBOOT: Device Scope entry @ 7c6a3f50:
>> TBOOT: Type: 0x1
>> TBOOT: Length: 0x8
>> TBOOT: Segment Number: 0x0
>> TBOOT: Starting Bus Number: 0x0
>> TBOOT: Raw PCI Path (Length - 4): 00 00 02 00
>>
>> TBOOT: VT-d DMAR table OK
>>
>>
>> Cihula, Joseph wrote:
>>>> From: Jonathan M. McCune [mailto:jon...@cm...]
>>>> Sent: Thursday, October 09, 2008 10:27 AM
>>>>
>>>> Hi Joe,
>>>>
>>>> Cihula, Joseph wrote:
>>>>> It is really:
>>>>> Current values of VT-d PMR registers do not match requested
>>>>> values in SinitMleData
>>>>>
>>>>> which means that some code has already programmed the PMRs but not
>>> to
>>>>> the same values that the MLE is requesting. Because the PMRs
>> cannot
>>>> be
>>>>> changed reliably once they are set/enabled, this is not an allowed
>>>>> condition.
>>>> I am successfully invoking SENTER / SEXIT and then returning
> control
>>> to
>>>> the legacy OS once per boot cycle. When I try to execute SENTER a
>>>> second time, the system reboots and LT.ERRORCODE is populated with
>> the
>>>> above error. However, I cannot figure out what is wrong with my
> PMR
>>>> values.
>>>>
>>>> Is there a way to read the current values, so that I can see how
>> they
>>>> are set following the first SENTER? Looking through the MLE manual
>> and
>>>> the Sw Dev Manual Vol 2b has left me without much insight.
>>> VT-d registers are described in the VT-d spec at:
>>>
> http://download.intel.com/technology/computing/vptech/Intel(r)_VT_for_D
>> i
>>> rect_IO.pdf
>>>
>>>> My MLE resides at physical address 0x00c00000 and consumes less
> than
>>>> 0x200000 (2MB) bytes.
>>>>
>>>> TBOOT: vtd_pmr_lo_base: 0xc00000
>>>> TBOOT: vtd_pmr_lo_size: 0x200000
>>>> TBOOT: vtd_pmr_hi_base: 0x0
>>>> TBOOT: vtd_pmr_hi_size: 0x0
>>>>
>>>> I'm fairly confident that the os_sinit_data_t.vtd_pmr_* values are
>>>> being
>>>> set identically prior to both invocations of SENTER (when I print
>> them
>>>> out, the above is what I see).
>>> If you could use the VT-d spec to read and output the PMRs before
>>> launch, that should determine if they are somehow getting changed
>>> between invocations.
>>>
>>>> Thanks,
>>>> -Jon
>
|
|
From: Cihula, J. <jos...@in...> - 2008-10-13 18:29:13
|
Based on some feedback from the recent Linux posting of the tboot/TXT patches as well as some enhancements that we've been looking at for tboot, there are some changes that we'd like to make to tboot that would not be backwards compatible with the existing Xen code. Naturally, we'd submit patches for Xen, but existing versions (e.g. 3.2, 3.3) would not work with the new tboot. The question I pose to those who use tboot with Xen is: how important is it that new versions of tboot continue to work with older versions of Xen? Joe |
15 messages has been excluded from this view by a project administrator.
