Thanks for the clarification.
On Mon, Feb 19, 2018, 17:33 Roger Pau Monné wrote:
> On Mon, Feb 19, 2018 at 05:13:11PM +, Wei Liu wrote:
> > On Mon, Feb 19, 2018 at 04:23:33PM +, Charles Gonçalves wrote:
> > > Hello,
> > >
> > > Im getting this Hypercall [op = 0x0040001a ] on xen trace b
On Mon, Feb 19, 2018 at 05:13:11PM +, Wei Liu wrote:
> On Mon, Feb 19, 2018 at 04:23:33PM +, Charles Gonçalves wrote:
> > Hello,
> >
> > Im getting this Hypercall [op = 0x0040001a ] on xen trace but can't figure
> > out which operation this is.
> >
> > Using old Xen 4.4.1.
> > Looking at
On Mon, Feb 19, 2018 at 04:23:33PM +, Charles Gonçalves wrote:
> Hello,
>
> Im getting this Hypercall [op = 0x0040001a ] on xen trace but can't figure
> out which operation this is.
>
> Using old Xen 4.4.1.
> Looking at documentation and also using grep into source code couldn't
> figure ou
On Mon, Feb 19, 2018 at 04:23:33PM +, Charles Gonçalves wrote:
> Hello,
>
> Im getting this Hypercall [op = 0x0040001a ] on xen trace but can't figure
> out which operation this is.
I guess 0x1a is the hypercall number (26 in decimal), which matches to
__HYPERVISOR_mmuext_op. See xen/include
