On Fri, 4 Nov 2016 01:39:31 +0800
Xiao Guangrong wrote:
>
>
> On 11/04/2016 01:29 AM, Igor Mammedov wrote:
> > On Fri, 4 Nov 2016 00:53:06 +0800
> > Xiao Guangrong wrote:
> >
> >>
> >>
> >> On 11/04/2016 12:49 AM, Igor Mammedov wrote:
> >>> On Fri, 4 Nov 2016 00:17:00 +0800
> >>> Xiao Guangron
On 11/04/2016 01:29 AM, Igor Mammedov wrote:
On Fri, 4 Nov 2016 00:53:06 +0800
Xiao Guangrong wrote:
On 11/04/2016 12:49 AM, Igor Mammedov wrote:
On Fri, 4 Nov 2016 00:17:00 +0800
Xiao Guangrong wrote:
On 11/04/2016 12:13 AM, Igor Mammedov wrote:
On Thu, 3 Nov 2016 22:53:43 +0800
Xi
On Fri, 4 Nov 2016 00:53:06 +0800
Xiao Guangrong wrote:
>
>
> On 11/04/2016 12:49 AM, Igor Mammedov wrote:
> > On Fri, 4 Nov 2016 00:17:00 +0800
> > Xiao Guangrong wrote:
> >
> >>
> >>
> >> On 11/04/2016 12:13 AM, Igor Mammedov wrote:
> >>> On Thu, 3 Nov 2016 22:53:43 +0800
> >>> Xiao Guangron
On 11/04/2016 12:49 AM, Igor Mammedov wrote:
On Fri, 4 Nov 2016 00:17:00 +0800
Xiao Guangrong wrote:
On 11/04/2016 12:13 AM, Igor Mammedov wrote:
On Thu, 3 Nov 2016 22:53:43 +0800
Xiao Guangrong wrote:
On 11/03/2016 10:49 PM, Igor Mammedov wrote:
On Thu, 3 Nov 2016 21:02:22 +0800
Xi
On Fri, 4 Nov 2016 00:17:00 +0800
Xiao Guangrong wrote:
>
>
> On 11/04/2016 12:13 AM, Igor Mammedov wrote:
> > On Thu, 3 Nov 2016 22:53:43 +0800
> > Xiao Guangrong wrote:
> >
> >>
> >>
> >> On 11/03/2016 10:49 PM, Igor Mammedov wrote:
> >>> On Thu, 3 Nov 2016 21:02:22 +0800
> >>> Xiao Guangron
On 11/04/2016 12:13 AM, Igor Mammedov wrote:
On Thu, 3 Nov 2016 22:53:43 +0800
Xiao Guangrong wrote:
On 11/03/2016 10:49 PM, Igor Mammedov wrote:
On Thu, 3 Nov 2016 21:02:22 +0800
Xiao Guangrong wrote:
On 11/03/2016 09:00 PM, Igor Mammedov wrote:
just drop this and describe prop
On Thu, 3 Nov 2016 22:53:43 +0800
Xiao Guangrong wrote:
>
>
> On 11/03/2016 10:49 PM, Igor Mammedov wrote:
> > On Thu, 3 Nov 2016 21:02:22 +0800
> > Xiao Guangrong wrote:
> >
> >>
> >>
> >> On 11/03/2016 09:00 PM, Igor Mammedov wrote:
> >>
> >>
> >>
> >>
> > just drop this and describe pro
On 11/03/2016 10:49 PM, Igor Mammedov wrote:
On Thu, 3 Nov 2016 21:02:22 +0800
Xiao Guangrong wrote:
On 11/03/2016 09:00 PM, Igor Mammedov wrote:
just drop this and describe properly 'len' in spec section
i.e. len: length of entire returned data (including the header)
Okay, i will c
On Thu, 3 Nov 2016 21:02:22 +0800
Xiao Guangrong wrote:
>
>
> On 11/03/2016 09:00 PM, Igor Mammedov wrote:
>
>
>
>
> >>> just drop this and describe properly 'len' in spec section
> >>> i.e. len: length of entire returned data (including the header)
> >>
> >> Okay, i will change the spec li
On 11/03/2016 09:00 PM, Igor Mammedov wrote:
just drop this and describe properly 'len' in spec section
i.e. len: length of entire returned data (including the header)
Okay, i will change the spec like this:
QEMU Writes Output Data (based on the offset in the page):
[0x0 - 0x3]:
On Thu, 3 Nov 2016 20:21:05 +0800
Xiao Guangrong wrote:
> On 11/03/2016 07:58 PM, Igor Mammedov wrote:
> > On Thu, 3 Nov 2016 11:51:29 +0800
> > Xiao Guangrong wrote:
> >
> >> _FIT is required for hotplug support, guest will inquire the updated
> >> device info from it if a hotplug event is r
On Thu, 3 Nov 2016 18:08:04 +0800
Xiao Guangrong wrote:
> On 11/03/2016 05:53 PM, Stefan Hajnoczi wrote:
> > On Thu, Nov 03, 2016 at 11:51:29AM +0800, Xiao Guangrong wrote:
> >> @@ -504,6 +521,77 @@ nvdimm_dsm_no_payload(uint32_t func_ret_status,
> >> hwaddr dsm_mem_addr)
> >> cpu_physica
On 11/03/2016 07:58 PM, Igor Mammedov wrote:
On Thu, 3 Nov 2016 11:51:29 +0800
Xiao Guangrong wrote:
_FIT is required for hotplug support, guest will inquire the updated
device info from it if a hotplug event is received
s/_FIT/_FIT method/
the same applies to subj. line
Okay.
As F
On Thu, 3 Nov 2016 11:51:29 +0800
Xiao Guangrong wrote:
> _FIT is required for hotplug support, guest will inquire the updated
> device info from it if a hotplug event is received
s/_FIT/_FIT method/
the same applies to subj. line
>
> As FIT buffer is not completely mapped into guest address
On 11/03/2016 05:53 PM, Stefan Hajnoczi wrote:
On Thu, Nov 03, 2016 at 11:51:29AM +0800, Xiao Guangrong wrote:
@@ -504,6 +521,77 @@ nvdimm_dsm_no_payload(uint32_t func_ret_status, hwaddr
dsm_mem_addr)
cpu_physical_memory_write(dsm_mem_addr, &out, sizeof(out));
}
+#define NVDIMM_DSM_RET
On Thu, Nov 03, 2016 at 11:51:29AM +0800, Xiao Guangrong wrote:
> @@ -504,6 +521,77 @@ nvdimm_dsm_no_payload(uint32_t func_ret_status, hwaddr
> dsm_mem_addr)
> cpu_physical_memory_write(dsm_mem_addr, &out, sizeof(out));
> }
>
> +#define NVDIMM_DSM_RET_STATUS_SUCCESS0 /* Success */
_FIT is required for hotplug support, guest will inquire the updated
device info from it if a hotplug event is received
As FIT buffer is not completely mapped into guest address space, so a
new function, Read FIT whose UUID is UUID
648B9CF2-CDA1-4312-8AD9-49C4AF32BD62, handle 0x1, function ind
17 matches
Mail list logo
