All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Cc: Keir Fraser <keir@xen.org>
Subject: Re: [PATCH 1/4] x86/HVM: replace plain number in hvm_combine_hw_exceptions()
Date: Thu, 22 Jan 2015 14:12:44 +0000	[thread overview]
Message-ID: <54C1055C.4030604@citrix.com> (raw)
In-Reply-To: <54C10FCD0200007800058291@mail.emea.novell.com>

On 22/01/15 13:57, Jan Beulich wrote:
> While doing so also take care of #VE here (even if we don't make use of
> it yet).
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -205,6 +205,16 @@ int hvm_event_needs_reinjection(uint8_t 
>   */
>  uint8_t hvm_combine_hw_exceptions(uint8_t vec1, uint8_t vec2)
>  {
> +    const unsigned int contributory_exceptions =
> +        (1 << TRAP_divide_error) |
> +        (1 << TRAP_invalid_tss) |
> +        (1 << TRAP_no_segment) |
> +        (1 << TRAP_stack_error) |
> +        (1 << TRAP_gp_fault);
> +    const unsigned int page_faults =
> +        (1 << TRAP_page_fault) |
> +        (1 << TRAP_virtualisation);

static as an extra hint?

I frankly hope that any decent compiler would turn these into
instruction immediate data.

Either way, Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>

(FWIW the 0x7c01 constant was the inspiration for my vlapic patch,
although I felt that constructing the map at compile time was better
than an opaque number.)

> +
>      /* Exception during double-fault delivery always causes a triple fault. */
>      if ( vec1 == TRAP_double_fault )
>      {
> @@ -213,11 +223,12 @@ uint8_t hvm_combine_hw_exceptions(uint8_
>      }
>  
>      /* Exception during page-fault delivery always causes a double fault. */
> -    if ( vec1 == TRAP_page_fault )
> +    if ( (1u << vec1) & page_faults )
>          return TRAP_double_fault;
>  
>      /* Discard the first exception if it's benign or if we now have a #PF. */
> -    if ( !((1u << vec1) & 0x7c01u) || (vec2 == TRAP_page_fault) )
> +    if ( !((1u << vec1) & contributory_exceptions) ||
> +         ((1u << vec2) & page_faults) )
>          return vec2;
>  
>      /* Cannot combine the exceptions: double fault. */
>
>
>

  reply	other threads:[~2015-01-22 14:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22 13:53 [PATCH 0/4] x86: replace plain numbers Jan Beulich
2015-01-22 13:57 ` [PATCH 1/4] x86/HVM: replace plain number in hvm_combine_hw_exceptions() Jan Beulich
2015-01-22 14:12   ` Andrew Cooper [this message]
2015-01-22 14:36     ` Jan Beulich
2015-01-22 14:42   ` Tim Deegan
2015-01-22 15:12     ` Jan Beulich
2015-01-22 15:27       ` Tim Deegan
2015-01-22 13:57 ` [PATCH 2/4] x86/HVM: replace plain numbers Jan Beulich
2015-01-22 14:41   ` Andrew Cooper
2015-01-22 15:17     ` Jan Beulich
2015-01-23 13:41       ` Andrew Cooper
2015-01-23 13:58         ` Jan Beulich
2015-01-23 13:59           ` Andrew Cooper
2015-01-22 14:00 ` [PATCH 3/4] x86/traps: " Jan Beulich
2015-01-22 14:45   ` Andrew Cooper
2015-01-22 14:01 ` [PATCH 4/4] VMX: " Jan Beulich
2015-01-22 15:21   ` Andrew Cooper
2015-01-23  6:25   ` Tian, Kevin

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=54C1055C.4030604@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.