qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin O'Connor <kevin@koconnor.net>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: kraxel@redhat.com, stefanha@gmail.com,
	Rob Bradford <robert.bradford@intel.com>,
	seabios@seabios.org, qemu-devel@nongnu.org,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Stephen Douthit <stephend@silicom-usa.com>,
	Stefan Berger <stefanb@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [SeaBIOS]  SeaBIOS booting time optimization
Date: Tue, 20 Nov 2018 10:55:00 -0500	[thread overview]
Message-ID: <20181120155500.GA29471@morn.lan> (raw)
In-Reply-To: <CAGxU2F4kUD85FMVEAcOpWUAGF98G2KR9O8EVAkzBDmA+DkS2KA@mail.gmail.com>

On Mon, Nov 19, 2018 at 07:38:39PM +0100, Stefano Garzarella wrote:
> just an update, I enabled the debug prints and I saw two timeouts fired
> with a lot
> of time lost (~780ms between "init timer" and "Scan for VGA ..."),
> putting other prints I discovered that a lot of time is spent in the
> tpm_setup(),
> during the probe of the 2 TPM devices:
> 
> 00.548869 init timer
> 00.549677 ./src/post.c:157 platform_hardware_setup
> 00.550182 ./src/hw/tpm_drivers.c:579 tpmhw_probe
> 01.300833 WARNING - Timeout at wait_reg8:81!
> 01.301388 ./src/hw/tpm_drivers.c:579 tpmhw_probe
> 01.331843 WARNING - Timeout at wait_reg8:81!
> 01.332316 ./src/post.c:160 platform_hardware_setup
> 01.333358 Scan for VGA option rom

FYI, this was raised a few months ago - see:

https://mail.coreboot.org/pipermail/seabios/2018-March/012186.html

IIRC, it should be possible to verify the TPM device is present before
trying to wait for it.

-Kevin

  parent reply	other threads:[~2018-11-20 15:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16 16:13 [Qemu-devel] SeaBIOS booting time optimization Stefano Garzarella
2018-11-16 16:39 ` Stefan Hajnoczi
2018-11-18 23:09   ` Samuel Ortiz
2018-11-18 23:31 ` Samuel Ortiz
2018-11-19 10:01   ` Stefano Garzarella
2018-11-19  8:48 ` Gerd Hoffmann
2018-11-19 10:42   ` Stefano Garzarella
2018-11-19 13:07     ` Stefan Hajnoczi
2018-11-19 14:15       ` Gerd Hoffmann
2018-11-19 18:38         ` Stefano Garzarella
2018-11-20  6:21           ` Gerd Hoffmann
2018-11-20  9:45             ` Stefano Garzarella
2018-11-20 11:22               ` Gerd Hoffmann
2018-11-22 11:08                 ` Stefano Garzarella
2018-11-22 11:51                   ` Gerd Hoffmann
2018-11-22 15:13                     ` Stefano Garzarella
2018-11-23  6:21                       ` Gerd Hoffmann
2018-11-23 11:18                         ` Stefano Garzarella
2018-11-23 15:54                           ` Kevin O'Connor
2018-11-23 16:30                             ` Stefano Garzarella
2018-11-20 15:55           ` Kevin O'Connor [this message]
2018-11-20 16:13             ` [Qemu-devel] [SeaBIOS] " Steve Douthit
2018-11-20 16:51               ` Stefano Garzarella
2018-11-21  5:43                 ` Stefan Berger
2018-11-28  2:08                   ` Kevin O'Connor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181120155500.GA29471@morn.lan \
    --to=kevin@koconnor.net \
    --cc=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=robert.bradford@intel.com \
    --cc=seabios@seabios.org \
    --cc=sgarzare@redhat.com \
    --cc=stefanb@linux.vnet.ibm.com \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.com \
    --cc=stephend@silicom-usa.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).