xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] x86/hvm: don't give vector callback higher priority than NMI/MCE
Date: Fri, 07 Sep 2012 15:47:54 +0100	[thread overview]
Message-ID: <CC6FC7AA.3E0B6%keir.xen@gmail.com> (raw)
In-Reply-To: <504A0BB50200007800099CD2@nat28.tlf.novell.com>

On 07/09/2012 13:59, "Jan Beulich" <JBeulich@suse.com> wrote:

> Those two should always be delivered first imo.
> 
> Signed-off-by: Jan Beulich <jbeulich@suse.com>

Acked-by: Keir Fraser <keir@xen.org>

> --- a/xen/arch/x86/hvm/irq.c
> +++ b/xen/arch/x86/hvm/irq.c
> @@ -395,16 +395,16 @@ struct hvm_intack hvm_vcpu_has_pending_i
>      struct hvm_domain *plat = &v->domain->arch.hvm_domain;
>      int vector;
>  
> -    if ( (plat->irq.callback_via_type == HVMIRQ_callback_vector)
> -         && vcpu_info(v, evtchn_upcall_pending) )
> -        return hvm_intack_vector(plat->irq.callback_via.vector);
> -
>      if ( unlikely(v->nmi_pending) )
>          return hvm_intack_nmi;
>  
>      if ( unlikely(v->mce_pending) )
>          return hvm_intack_mce;
>  
> +    if ( (plat->irq.callback_via_type == HVMIRQ_callback_vector)
> +         && vcpu_info(v, evtchn_upcall_pending) )
> +        return hvm_intack_vector(plat->irq.callback_via.vector);
> +
>      if ( vlapic_accept_pic_intr(v) && plat->vpic[0].int_output )
>          return hvm_intack_pic(0);
>  
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2012-09-07 14:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 12:59 [PATCH] x86/hvm: don't give vector callback higher priority than NMI/MCE Jan Beulich
2012-09-07 14:47 ` Keir Fraser [this message]
2012-09-10 13:49 ` Stefano Stabellini

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=CC6FC7AA.3E0B6%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.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 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).