Thanks for all your comments. I'm going to write a simple demo to go
through the whole workflow first, and then adjust the policies following
the conclusions of our discussion.
Heyi
On 2019/7/16 16:47, Dave Martin wrote:
On Mon, Jul 15, 2019 at 03:44:46PM +0100, Mark Rutland wrote:
On Mon,
On Mon, Jul 15, 2019 at 03:44:46PM +0100, Mark Rutland wrote:
> On Mon, Jul 15, 2019 at 03:26:39PM +0100, James Morse wrote:
> > On 15/07/2019 14:48, Mark Rutland wrote:
> > > On Mon, Jul 15, 2019 at 02:41:00PM +0100, Dave Martin wrote:
> > >> One option (suggested to me by James Morse) would be to
On 16/07/2019 09:30, Dave Martin wrote:
> On Mon, Jul 15, 2019 at 02:48:49PM +0100, Mark Rutland wrote:
>> On Mon, Jul 15, 2019 at 02:41:00PM +0100, Dave Martin wrote:
>
> [...]
>
>>> So long as KVM_EXIT_HYPERCALL reports sufficient information so that
>>> userspace can identify the cause as an S
On Mon, Jul 15, 2019 at 02:48:49PM +0100, Mark Rutland wrote:
> On Mon, Jul 15, 2019 at 02:41:00PM +0100, Dave Martin wrote:
[...]
> > So long as KVM_EXIT_HYPERCALL reports sufficient information so that
> > userspace can identify the cause as an SMC and retrieve the SMC
> > immediate field, this
On Mon, Jul 15, 2019 at 03:26:39PM +0100, James Morse wrote:
> On 15/07/2019 14:48, Mark Rutland wrote:
> > On Mon, Jul 15, 2019 at 02:41:00PM +0100, Dave Martin wrote:
> >> One option (suggested to me by James Morse) would be to allow userspace
> >> to disable in the in-kernel PSCI implementation
Hi guys,
On 15/07/2019 14:48, Mark Rutland wrote:
> On Mon, Jul 15, 2019 at 02:41:00PM +0100, Dave Martin wrote:
>> On Sat, Jul 13, 2019 at 05:53:57PM +0800, Guoheyi wrote:
>>> Do it make sense to implement virtual SDEI in qemu? So that we can have the
>>> standard way for guest to handle NMI watc
On Mon, Jul 15, 2019 at 02:41:00PM +0100, Dave Martin wrote:
> On Sat, Jul 13, 2019 at 05:53:57PM +0800, Guoheyi wrote:
> > Hi folks,
> >
> > Do it make sense to implement virtual SDEI in qemu? So that we can have the
> > standard way for guest to handle NMI watchdog, RAS events and something else
On Sat, Jul 13, 2019 at 05:53:57PM +0800, Guoheyi wrote:
> Hi folks,
>
> Do it make sense to implement virtual SDEI in qemu? So that we can have the
> standard way for guest to handle NMI watchdog, RAS events and something else
> which involves SDEI in a physical ARM64 machine.
>
> My basic idea
Hi folks,
Do it make sense to implement virtual SDEI in qemu? So that we can have
the standard way for guest to handle NMI watchdog, RAS events and
something else which involves SDEI in a physical ARM64 machine.
My basic idea is like below:
1. Change a few lines of code in kvm to allow unhan
