On Tue, 28 Feb 2017, Julien Grall wrote:
> Hi Stefano,
>
> On 22/02/17 17:29, Stefano Stabellini wrote:
> > Introduce new Xen command line parameter called "vwfi", which stands for
> > virtual wfi. The default is "trap": Xen traps the guest wfi instruction
> > and calls vcpu_block on the guest vcp
Hi Stefano,
On 22/02/17 17:29, Stefano Stabellini wrote:
Introduce new Xen command line parameter called "vwfi", which stands for
virtual wfi. The default is "trap": Xen traps the guest wfi instruction
and calls vcpu_block on the guest vcpu. The behavior can be changed
setting vwfi to "native",
On Wed, Feb 22, 2017 at 09:29:47AM -0800, Stefano Stabellini wrote:
> Introduce new Xen command line parameter called "vwfi", which stands for
> virtual wfi. The default is "trap": Xen traps the guest wfi instruction
> and calls vcpu_block on the guest vcpu. The behavior can be changed
> setting vw
Introduce new Xen command line parameter called "vwfi", which stands for
virtual wfi. The default is "trap": Xen traps the guest wfi instruction
and calls vcpu_block on the guest vcpu. The behavior can be changed
setting vwfi to "native", in that case Xen doesn't trap the instruction
at all, runnin
