From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Boot time trap handling Date: Mon, 12 May 2014 14:01:14 +0100 Message-ID: <5370C61A.4000505@citrix.com> References: <5370A527.3000406@citrix.com> <5370D6210200007800011617@mail.emea.novell.com> <5370C443.9030906@citrix.com> <5370E1B70200007800011690@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5370E1B70200007800011690@mail.emea.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: TimDeegan , Keir Fraser , Xen-devel List List-Id: xen-devel@lists.xenproject.org On 12/05/14 13:59, Jan Beulich wrote: >>>> On 12.05.14 at 14:53, wrote: >> One point I forgot to say was that I plan to leave the reserved >> exception vectors with non-present descriptors. This way we get a fatal >> GPF indicating the exact vector, rather than a PCPU lockup optionally >> followed by an NMI watchdog timeout when another pcpu times out waiting >> for the locked up pcpu to rendezvous in the time calibration code. > This I'm not sure about. Replacing the simplistic handler is a must of > course, but I would tend towards a generic exception handler wired > up to fatal_trap() rather than having to decode the #GP error code > to understand what's going on. > > Jan > Ok - I will make a formal entry point for each of the reserved exceptions. ~Andrew