Re: [PATCH] Implement timekeeping for rumprun/hw (x86)

  • From: Martin Lucina <martin@xxxxxxxxxx>
  • To: rumpkernel-users@xxxxxxxxxxxxx
  • Date: Mon, 6 Jul 2015 16:43:26 +0200

On Saturday, 04.07.2015 at 17:47, Martin Lucina wrote:

On Saturday, 04.07.2015 at 11:30, Antti Kantee wrote:
You missed the "make *sure* the user sees the error" part. How else
are you going to do that except by printing the warning and then
refusing to boot by default? If you refuse to boot by default, how
else are going let the user to decide to force boot anyway except
with an override switch in rumprun? (probably some other ways, but
that was the most obvious way for my imagination)

I don't want to ship a system with weird bugs where the blame is on
the user for not studying the full boot output on every system they
deploy on.

Good point, In that case, yeah, refusing to boot by default is probably the
best option.

I have put in a check that halts on boot if RDTSC is not supported at all.

I have also put in a check that warns if the "TSC invariant" bit is not set
in CPUID, however it turns out that neither KVM nor QEMU set this on my
system, possibly on purpose. So halting if that flag is not set would not
be very useful :-/



Other related posts: