Re: [Xen-devel] [PATCH v4 2/7] x86/hyperv: setup hypercall page

2020-01-28 Thread Jan Beulich
On 28.01.2020 16:30, Wei Liu wrote: > On Thu, Jan 23, 2020 at 12:18:41PM +0100, Jan Beulich wrote: >> On 22.01.2020 21:23, Wei Liu wrote: >>> --- a/xen/arch/x86/e820.c >>> +++ b/xen/arch/x86/e820.c >>> @@ -36,6 +36,22 @@ boolean_param("e820-verbose", e820_verbose); >>> struct e820map e820; >>>

Re: [Xen-devel] [PATCH v4 2/7] x86/hyperv: setup hypercall page

2020-01-28 Thread Wei Liu
On Thu, Jan 23, 2020 at 12:18:41PM +0100, Jan Beulich wrote: > On 22.01.2020 21:23, Wei Liu wrote: > > --- a/xen/arch/x86/e820.c > > +++ b/xen/arch/x86/e820.c > > @@ -36,6 +36,22 @@ boolean_param("e820-verbose", e820_verbose); > > struct e820map e820; > > struct e820map __initdata e820_raw; > >

Re: [Xen-devel] [PATCH v4 2/7] x86/hyperv: setup hypercall page

2020-01-28 Thread Wei Liu
On Thu, Jan 23, 2020 at 01:35:22AM +, Michael Kelley wrote: [...] > > diff --git a/xen/include/asm-x86/guest/hyperv-tlfs.h b/xen/include/asm- > > x86/guest/hyperv-tlfs.h > > index 05c4044976..5d37efd2d2 100644 > > --- a/xen/include/asm-x86/guest/hyperv-tlfs.h > > +++

Re: [Xen-devel] [PATCH v4 2/7] x86/hyperv: setup hypercall page

2020-01-28 Thread Wei Liu
On Wed, Jan 22, 2020 at 09:31:52PM +, Andrew Cooper wrote: > On 22/01/2020 20:23, Wei Liu wrote: > > Use the top-most addressable page for that purpose. Adjust e820 code > > accordingly. > > > > We also need to register Xen's guest OS ID to Hyper-V. Use 0x300 as the > > OS type. > > > >

Re: [Xen-devel] [PATCH v4 2/7] x86/hyperv: setup hypercall page

2020-01-23 Thread Michael Kelley
From: Jan Beulich Sent: Thursday, January 23, 2020 3:19 AM > > On 22.01.2020 21:23, Wei Liu wrote: > > --- a/xen/arch/x86/e820.c > > +++ b/xen/arch/x86/e820.c > > @@ -36,6 +36,22 @@ boolean_param("e820-verbose", e820_verbose); > > struct e820map e820; > > struct e820map __initdata e820_raw; >

Re: [Xen-devel] [PATCH v4 2/7] x86/hyperv: setup hypercall page

2020-01-23 Thread Jan Beulich
On 22.01.2020 21:23, Wei Liu wrote: > --- a/xen/arch/x86/e820.c > +++ b/xen/arch/x86/e820.c > @@ -36,6 +36,22 @@ boolean_param("e820-verbose", e820_verbose); > struct e820map e820; > struct e820map __initdata e820_raw; > > +static unsigned int find_phys_addr_bits(void) > +{ > +uint32_t

Re: [Xen-devel] [PATCH v4 2/7] x86/hyperv: setup hypercall page

2020-01-23 Thread Jan Beulich
On 22.01.2020 22:31, Andrew Cooper wrote: > On 22/01/2020 20:23, Wei Liu wrote: >> --- a/xen/arch/x86/e820.c >> +++ b/xen/arch/x86/e820.c >> + */ >> +unsigned int phys_bits = find_phys_addr_bits(); >> +unsigned long hcall_pfn = >> + ((1ull << phys_bits) - 1) >>

Re: [Xen-devel] [PATCH v4 2/7] x86/hyperv: setup hypercall page

2020-01-22 Thread Michael Kelley
From: Wei Liu On Behalf Of Wei Liu Sent: Wednesday, January 22, 2020 12:24 PM > > Use the top-most addressable page for that purpose. Adjust e820 code > accordingly. > > We also need to register Xen's guest OS ID to Hyper-V. Use 0x300 as the > OS type. > > Signed-off-by: Wei Liu > --- > XXX

Re: [Xen-devel] [PATCH v4 2/7] x86/hyperv: setup hypercall page

2020-01-22 Thread Andrew Cooper
On 22/01/2020 20:23, Wei Liu wrote: > Use the top-most addressable page for that purpose. Adjust e820 code > accordingly. > > We also need to register Xen's guest OS ID to Hyper-V. Use 0x300 as the > OS type. > > Signed-off-by: Wei Liu > --- > XXX the decision on Xen's vendor ID is pending.

[Xen-devel] [PATCH v4 2/7] x86/hyperv: setup hypercall page

2020-01-22 Thread Wei Liu
Use the top-most addressable page for that purpose. Adjust e820 code accordingly. We also need to register Xen's guest OS ID to Hyper-V. Use 0x300 as the OS type. Signed-off-by: Wei Liu --- XXX the decision on Xen's vendor ID is pending. v4: 1. Use fixmap 2. Follow routines listed in TLFS ---