Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.arch > #118931

Re: Interrupts in OoO

Show all headers | View raw

George Neuner <gneuner2@comcast.net> posted:

> On Wed, 28 Oct 2026 15:35:45 GMT, MitchAlsup
> <user5857@newsgrouper.org.invalid> wrote:
> 
> >scott@slp53.sl.home (Scott Lurndal) posted:
> >
> >> MitchAlsup <user5857@newsgrouper.org.invalid> writes:
> >> >scott@slp53.sl.home (Scott Lurndal) posted:
> >> >
> >> >> MitchAlsup <user5857@newsgrouper.org.invalid> writes:
> >> >-----------------------------
> >> >> >> In my terminology I have Exceptions, Interrupts, and Errors.
> >> >> >> I take all the well defined stuff and put it in the Exception and
> >> >> >> Interrupt buckets, and take all the weird stuff and call it Errors.
> >> >> >
> >> >> >To a very large extent I agree with you. The things you call errors
> >> >> >I call Checks. Checks are never supposed to happen {{like late store
> >> >> >data ECC fails}}.
> >> >> 
> >> >> If it is "never supposed to happen", why bother to check at all...
> >> >
> >> >Guest OS can run as if uncorrectable ECC can never happen. So, to
> >> >Guest OS it is never supposed to happen, and Guest OS is not setup
> >> >to deal with the problem if it does.
> >> >
> >> >HyperVisor cannot run banking applications with UC ECC, whereas some
> >> >real-time control might be able to; so you punt it all the way up the
> >> >privilege ladder.
> >> > 
> >> >> For RAS reasons, if nothing else, one must assume that anything
> >> >> may happen.
> >> >
> >> >But, still, Guest OS should not be burdened with those checks.
> >> 
> >> Nor should the hypervisor.  All of which are generally hardware
> >> agnostic (KVM, XEN, VMWare, et alia) for most everything except
> >> the virtualization mechanics (AMD's SVM or Intel's VM capabilities).
> >
> >So, it all one has is {user, Guest, Host, Hyper}: who SHOULD be burdened
> >with creating responses to things that are not supposed to happen but do ??
> 
> There is another question along with who handles it ... what should be
> done?  Uncorrected ECC error (check) means the data has to be
> considered corrupt [even if it really is valid] and unusable.
> 
> Do you crash the program that can't handle it?

Real Time control--just move along
.....
Banking--recover to checkpoint
4,000 hour GB FP application--recover to checkpoint

> Do you crash the guest OS that can't handle it?

PC--take a crash or restart Guest OS
Server--backup to checkpoint and run forward until you catchup with real-time
   :
> How is the user going to feel about your system?

Better than if the error was never detected...

Back to comp.arch | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Re: Interrupts in OoO (was: Microarchitectural support for counting) quadibloc@invalid.com (John Savard) - 2026-10-23 23:57 +0000
  Re: Interrupts in OoO Robert Finch <robfi680@gmail.com> - 2026-10-23 21:12 -0400
  Re: Interrupts in OoO (was: Microarchitectural support for counting) MitchAlsup <user5857@newsgrouper.org.invalid> - 2026-10-24 19:20 +0000
    Re: Interrupts in OoO (was: Microarchitectural support for counting) scott@slp53.sl.home (Scott Lurndal) - 2026-10-25 15:53 +0000
      Re: Interrupts in OoO EricP <ThatWouldBeTelling@thevillage.com> - 2026-10-26 11:06 -0400
        Re: Interrupts in OoO Robert Finch <robfi680@gmail.com> - 2026-10-26 13:17 -0400
          Re: Interrupts in OoO EricP <ThatWouldBeTelling@thevillage.com> - 2026-10-26 17:03 -0400
            Re: Interrupts in OoO "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-26 14:14 -0700
              Re: Interrupts in OoO EricP <ThatWouldBeTelling@thevillage.com> - 2026-10-28 14:39 -0400
                Re: Interrupts in OoO "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-28 15:10 -0700
                Re: Interrupts in OoO EricP <ThatWouldBeTelling@thevillage.com> - 2026-10-29 14:50 -0400
            Re: Interrupts in OoO MitchAlsup <user5857@newsgrouper.org.invalid> - 2026-10-27 16:48 +0000
        Re: Interrupts in OoO MitchAlsup <user5857@newsgrouper.org.invalid> - 2026-10-27 16:35 +0000
          Re: Interrupts in OoO scott@slp53.sl.home (Scott Lurndal) - 2026-10-27 18:33 +0000
            Re: Interrupts in OoO MitchAlsup <user5857@newsgrouper.org.invalid> - 2026-10-27 21:07 +0000
              Re: Interrupts in OoO scott@slp53.sl.home (Scott Lurndal) - 2026-10-27 21:17 +0000
                Re: Interrupts in OoO MitchAlsup <user5857@newsgrouper.org.invalid> - 2026-10-28 15:35 +0000
                Re: Interrupts in OoO George Neuner <gneuner2@comcast.net> - 2026-10-28 14:34 -0400
                Re: Interrupts in OoO scott@slp53.sl.home (Scott Lurndal) - 2026-10-28 20:16 +0000
                Re: Interrupts in OoO MitchAlsup <user5857@newsgrouper.org.invalid> - 2026-10-29 02:17 +0000
                Re: Interrupts in OoO "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-10-28 21:21 -0700
                Re: Interrupts in OoO George Neuner <gneuner2@comcast.net> - 2026-10-29 21:49 -0400
              Re: Interrupts in OoO EricP <ThatWouldBeTelling@thevillage.com> - 2026-10-28 14:57 -0400
                Re: Interrupts in OoO MitchAlsup <user5857@newsgrouper.org.invalid> - 2026-10-29 02:27 +0000
          Re: Interrupts in OoO EricP <ThatWouldBeTelling@thevillage.com> - 2026-10-28 14:19 -0400
            Re: Interrupts in OoO MitchAlsup <user5857@newsgrouper.org.invalid> - 2026-10-28 19:02 +0000
  Re: Interrupts in OoO (was: Microarchitectural support for counting) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-10-26 17:45 +0000
    Re: Interrupts in OoO (was: Microarchitectural support for counting) MitchAlsup <user5857@newsgrouper.org.invalid> - 2026-10-27 16:39 +0000

csiph-web