Re: [Xen-devel] [PATCH-v2] xen: Don't call arch_trigger_all_cpu_backtracein dom0(pvm)

[Zhenzhong Duan]

On 2013-04-10 00:36, Ian Campbell wrote:
> On Mon, 2013-04-08 at 08:42 +0100, Jan Beulich wrote:
> > > > > On 07.04.13 at 07:54, Zhenzhong Duan <zhenzhong.duan@xxxxxxxxxx> wrote:
> > > nmi isn't supported in dom0, fallback to general all cpu backtrace code.
> > Since when is sending NMIs not supported, and since when is this
> > Dom0-specific? If you want to deal with this, you should do so
> > properly: Special case sending NMIs in the respective Xen specific
> > code (using VCPUOP_send_nmi), and carry this out in a way not
> > dependent upon running (un)privileged.
> You'd also need to implement the upcall support for receiving NMIs,
> which IIRC isn't yet done for pvops.
Hi Ian,

Could you give a suggestion on which file to change to support NMI upcall?
I compare with vMCE code, made similar change.
Use VCPUOP_send_nmi to send nmi between pvm guest vcpus, but nmi isn't 
triggered.

thanks
zduan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/