From: David Vrabel <david.vrabel@citrix.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
David Vrabel <david.vrabel@citrix.com>
Cc: <xen-devel@lists.xenproject.org>,
Andrew Jones <drjones@redhat.com>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH v2] xenpv: don't BUG when failing to setup NMI callback
Date: Mon, 16 Jun 2014 17:37:10 +0100 [thread overview]
Message-ID: <539F1D36.5040008@citrix.com> (raw)
In-Reply-To: <1402916820-27500-1-git-send-email-vkuznets@redhat.com>
On 16/06/14 12:07, Vitaly Kuznetsov wrote:
>
> --- a/arch/x86/xen/enlighten.c
> +++ b/arch/x86/xen/enlighten.c
> @@ -746,12 +746,13 @@ static int cvt_gate_to_trap(int vector, const gate_desc *val,
> */
> ;
> #endif
> - } else if (addr == (unsigned long)nmi)
> + } else if (addr == (unsigned long)nmi) {
> /*
> - * Use the native version as well.
> + * Use the native version as well but require Xen >= 3.2
> */
> - ;
> - else {
> + if (!xen_running_on_version_or_later(3, 2))
> + return 0;
> + } else {
The end result of this looked odd so I played around with it a bit and
it turns out that the register_callback for the NMI is entirely unneeded
(since we set the NMI callback via the write_idt pv-op and it's also
broken since it only sets the callback on the current VCPU.
I'm preparing an alternate patch, but I do not have a Xen 3.1 install I
can test with.
David
prev parent reply other threads:[~2014-06-16 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 11:07 [PATCH v2] xenpv: don't BUG when failing to setup NMI callback Vitaly Kuznetsov
2014-06-16 14:22 ` Konrad Rzeszutek Wilk
2014-06-16 14:22 ` Konrad Rzeszutek Wilk
2014-06-16 16:37 ` David Vrabel
2014-06-16 16:37 ` David Vrabel [this message]
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=539F1D36.5040008@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=drjones@redhat.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vkuznets@redhat.com \
--cc=x86@kernel.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.