On 08/11/2019 00:04, Colin Percival wrote:
> On 2019-11-07 13:34, Andriy Gapon wrote:
>> On 07/11/2019 23:19, Colin Percival wrote:
>>> On 2019-11-07 13:14, Andriy Gapon wrote:
x86 stack_save_td_running() can work safely only if IPI_TRACE is a
non-maskable interrupt. But at the
On 2019-11-07 13:34, Andriy Gapon wrote:
> On 07/11/2019 23:19, Colin Percival wrote:
>> On 2019-11-07 13:14, Andriy Gapon wrote:
>>> x86 stack_save_td_running() can work safely only if IPI_TRACE is a
>>> non-maskable interrupt. But at the moment FreeBSD/Xen does not provide
>>> support for
On 07/11/2019 23:19, Colin Percival wrote:
> On 2019-11-07 13:14, Andriy Gapon wrote:
>> x86 stack_save_td_running() can work safely only if IPI_TRACE is a
>> non-maskable interrupt. But at the moment FreeBSD/Xen does not provide
>> support for the NMI delivery mode. So, mark the
On 2019-11-07 13:14, Andriy Gapon wrote:
> x86 stack_save_td_running() can work safely only if IPI_TRACE is a
> non-maskable interrupt. But at the moment FreeBSD/Xen does not provide
> support for the NMI delivery mode. So, mark the functionality as
> unsupported similarly to other
Author: avg
Date: Thu Nov 7 21:14:59 2019
New Revision: 354482
URL: https://svnweb.freebsd.org/changeset/base/354482
Log:
IPI_TRACE is not really supported on xen
x86 stack_save_td_running() can work safely only if IPI_TRACE is a
non-maskable interrupt. But at the moment FreeBSD/Xen
