On 02/19/2016 04:08 PM, Michael S. Tsirkin wrote:
On Thu, Feb 18, 2016 at 11:05:23AM +0100, Igor Mammedov wrote:
On Thu, 18 Feb 2016 12:03:36 +0800
Xiao Guangrong wrote:
On 02/18/2016 01:26 AM, Michael S. Tsirkin wrote:
On Wed, Feb 17, 2016 at 10:04:18AM
On 02/19/2016 04:43 PM, Dan Williams wrote:
On Fri, Feb 19, 2016 at 12:08 AM, Michael S. Tsirkin wrote:
On Thu, Feb 18, 2016 at 11:05:23AM +0100, Igor Mammedov wrote:
On Thu, 18 Feb 2016 12:03:36 +0800
Xiao Guangrong wrote:
On 02/18/2016
On Fri, Feb 19, 2016 at 12:08 AM, Michael S. Tsirkin wrote:
> On Thu, Feb 18, 2016 at 11:05:23AM +0100, Igor Mammedov wrote:
>> On Thu, 18 Feb 2016 12:03:36 +0800
>> Xiao Guangrong wrote:
>>
>> > On 02/18/2016 01:26 AM, Michael S. Tsirkin wrote:
On Thu, Feb 18, 2016 at 11:05:23AM +0100, Igor Mammedov wrote:
> On Thu, 18 Feb 2016 12:03:36 +0800
> Xiao Guangrong wrote:
>
> > On 02/18/2016 01:26 AM, Michael S. Tsirkin wrote:
> > > On Wed, Feb 17, 2016 at 10:04:18AM +0800, Xiao Guangrong wrote:
> > > As
On Thu, Feb 18, 2016 at 12:03:36PM +0800, Xiao Guangrong wrote:
>
>
> On 02/18/2016 01:26 AM, Michael S. Tsirkin wrote:
> >On Wed, Feb 17, 2016 at 10:04:18AM +0800, Xiao Guangrong wrote:
> >As for the rest could that commands go via MMIO that we usually
> >use for control path?
>
>
On Thu, 18 Feb 2016 12:03:36 +0800
Xiao Guangrong wrote:
> On 02/18/2016 01:26 AM, Michael S. Tsirkin wrote:
> > On Wed, Feb 17, 2016 at 10:04:18AM +0800, Xiao Guangrong wrote:
> > As for the rest could that commands go via MMIO that we usually
> > use
On 02/18/2016 01:26 AM, Michael S. Tsirkin wrote:
On Wed, Feb 17, 2016 at 10:04:18AM +0800, Xiao Guangrong wrote:
As for the rest could that commands go via MMIO that we usually
use for control path?
So both input data and output data go through single MMIO, we need to
introduce a protocol
On Wed, Feb 17, 2016 at 10:04:18AM +0800, Xiao Guangrong wrote:
> >>>As for the rest could that commands go via MMIO that we usually
> >>>use for control path?
> >>
> >>So both input data and output data go through single MMIO, we need to
> >>introduce a protocol to pass these data, that is
On 02/16/2016 07:00 PM, Igor Mammedov wrote:
On Tue, 16 Feb 2016 02:35:41 +0800
Xiao Guangrong wrote:
On 02/16/2016 01:24 AM, Igor Mammedov wrote:
On Mon, 15 Feb 2016 23:53:13 +0800
Xiao Guangrong wrote:
On 02/15/2016 09:32
On Tue, 16 Feb 2016 02:35:41 +0800
Xiao Guangrong wrote:
> On 02/16/2016 01:24 AM, Igor Mammedov wrote:
> > On Mon, 15 Feb 2016 23:53:13 +0800
> > Xiao Guangrong wrote:
> >
> >> On 02/15/2016 09:32 PM, Igor Mammedov wrote:
>
On 02/16/2016 01:24 AM, Igor Mammedov wrote:
On Mon, 15 Feb 2016 23:53:13 +0800
Xiao Guangrong wrote:
On 02/15/2016 09:32 PM, Igor Mammedov wrote:
On Mon, 15 Feb 2016 13:45:59 +0200
"Michael S. Tsirkin" wrote:
On Mon, Feb 15, 2016 at
On Mon, 15 Feb 2016 23:53:13 +0800
Xiao Guangrong wrote:
> On 02/15/2016 09:32 PM, Igor Mammedov wrote:
> > On Mon, 15 Feb 2016 13:45:59 +0200
> > "Michael S. Tsirkin" wrote:
> >
> >> On Mon, Feb 15, 2016 at 11:47:42AM +0100, Igor Mammedov
On 02/15/2016 09:32 PM, Igor Mammedov wrote:
On Mon, 15 Feb 2016 13:45:59 +0200
"Michael S. Tsirkin" wrote:
On Mon, Feb 15, 2016 at 11:47:42AM +0100, Igor Mammedov wrote:
On Mon, 15 Feb 2016 18:13:38 +0800
Xiao Guangrong wrote:
On
On Mon, 15 Feb 2016 13:45:59 +0200
"Michael S. Tsirkin" wrote:
> On Mon, Feb 15, 2016 at 11:47:42AM +0100, Igor Mammedov wrote:
> > On Mon, 15 Feb 2016 18:13:38 +0800
> > Xiao Guangrong wrote:
> >
> > > On 02/15/2016 05:18 PM, Michael S.
On Mon, Feb 15, 2016 at 11:47:42AM +0100, Igor Mammedov wrote:
> On Mon, 15 Feb 2016 18:13:38 +0800
> Xiao Guangrong wrote:
>
> > On 02/15/2016 05:18 PM, Michael S. Tsirkin wrote:
> > > On Mon, Feb 15, 2016 at 10:11:05AM +0100, Igor Mammedov wrote:
> > >> On
On Mon, Feb 15, 2016 at 06:13:38PM +0800, Xiao Guangrong wrote:
>
>
> On 02/15/2016 05:18 PM, Michael S. Tsirkin wrote:
> >On Mon, Feb 15, 2016 at 10:11:05AM +0100, Igor Mammedov wrote:
> >>On Sun, 14 Feb 2016 13:57:27 +0800
> >>Xiao Guangrong wrote:
> >>
> >>>On
On 02/15/2016 06:47 PM, Igor Mammedov wrote:
On Mon, 15 Feb 2016 18:13:38 +0800
Xiao Guangrong wrote:
On 02/15/2016 05:18 PM, Michael S. Tsirkin wrote:
On Mon, Feb 15, 2016 at 10:11:05AM +0100, Igor Mammedov wrote:
On Sun, 14 Feb 2016 13:57:27 +0800
Xiao
On Mon, 15 Feb 2016 18:13:38 +0800
Xiao Guangrong wrote:
> On 02/15/2016 05:18 PM, Michael S. Tsirkin wrote:
> > On Mon, Feb 15, 2016 at 10:11:05AM +0100, Igor Mammedov wrote:
> >> On Sun, 14 Feb 2016 13:57:27 +0800
> >> Xiao Guangrong
On Mon, Feb 15, 2016 at 06:13:38PM +0800, Xiao Guangrong wrote:
>
>
> On 02/15/2016 05:18 PM, Michael S. Tsirkin wrote:
> >On Mon, Feb 15, 2016 at 10:11:05AM +0100, Igor Mammedov wrote:
> >>On Sun, 14 Feb 2016 13:57:27 +0800
> >>Xiao Guangrong wrote:
> >>
> >>>On
On 02/15/2016 05:18 PM, Michael S. Tsirkin wrote:
On Mon, Feb 15, 2016 at 10:11:05AM +0100, Igor Mammedov wrote:
On Sun, 14 Feb 2016 13:57:27 +0800
Xiao Guangrong wrote:
On 02/08/2016 07:03 PM, Igor Mammedov wrote:
On Wed, 13 Jan 2016 02:50:05 +0800
Xiao
On Mon, Feb 15, 2016 at 10:11:05AM +0100, Igor Mammedov wrote:
> On Sun, 14 Feb 2016 13:57:27 +0800
> Xiao Guangrong wrote:
>
> > On 02/08/2016 07:03 PM, Igor Mammedov wrote:
> > > On Wed, 13 Jan 2016 02:50:05 +0800
> > > Xiao Guangrong
On Sun, 14 Feb 2016 13:57:27 +0800
Xiao Guangrong wrote:
> On 02/08/2016 07:03 PM, Igor Mammedov wrote:
> > On Wed, 13 Jan 2016 02:50:05 +0800
> > Xiao Guangrong wrote:
> >
> >> 32 bits IO port starting from 0x0a18 in guest is
On 02/08/2016 07:03 PM, Igor Mammedov wrote:
On Wed, 13 Jan 2016 02:50:05 +0800
Xiao Guangrong wrote:
32 bits IO port starting from 0x0a18 in guest is reserved for NVDIMM
ACPI emulation. The table, NVDIMM_DSM_MEM_FILE, will be patched into
NVDIMM ACPI binary
On Wed, 13 Jan 2016 02:50:05 +0800
Xiao Guangrong wrote:
> 32 bits IO port starting from 0x0a18 in guest is reserved for NVDIMM
> ACPI emulation. The table, NVDIMM_DSM_MEM_FILE, will be patched into
> NVDIMM ACPI binary code
>
> OSPM uses this port to tell QEMU
On Wed, Jan 13, 2016 at 02:50:05AM +0800, Xiao Guangrong wrote:
> 32 bits IO port starting from 0x0a18 in guest is reserved for NVDIMM
> ACPI emulation. The table, NVDIMM_DSM_MEM_FILE, will be patched into
> NVDIMM ACPI binary code
>
> OSPM uses this port to tell QEMU the final address of the DSM
32 bits IO port starting from 0x0a18 in guest is reserved for NVDIMM
ACPI emulation. The table, NVDIMM_DSM_MEM_FILE, will be patched into
NVDIMM ACPI binary code
OSPM uses this port to tell QEMU the final address of the DSM memory
and notify QEMU to emulate the DSM method
Signed-off-by: Xiao
26 matches
Mail list logo