On Mon, 7 Mar 2016 18:19:46 +0200
"Michael S. Tsirkin" wrote:
> On Mon, Mar 07, 2016 at 05:17:19PM +0100, Igor Mammedov wrote:
> > > > So what would happen when PCI MMIO BAR would be mapped over above range,
> > > > since guest thinks it's free to use it as unused resource?
> > >
> > > IIRC,
On Mon, Mar 07, 2016 at 05:17:19PM +0100, Igor Mammedov wrote:
> > > So what would happen when PCI MMIO BAR would be mapped over above range,
> > > since guest thinks it's free to use it as unused resource?
> >
> > IIRC, allocating MMIO BAR over RAM would make the MMIO invisible,
> > irrespectiv
On Mon, 7 Mar 2016 17:09:32 +0200
"Michael S. Tsirkin" wrote:
> On Mon, Mar 07, 2016 at 03:49:47PM +0100, Igor Mammedov wrote:
> > On Mon, 7 Mar 2016 14:22:38 +0200
> > "Michael S. Tsirkin" wrote:
> >
> > > On Mon, Mar 07, 2016 at 01:16:48PM +0100, Igor Mammedov wrote:
> > > > On Thu, 3 Mar
On Mon, Mar 07, 2016 at 03:49:47PM +0100, Igor Mammedov wrote:
> On Mon, 7 Mar 2016 14:22:38 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Mon, Mar 07, 2016 at 01:16:48PM +0100, Igor Mammedov wrote:
> > > On Thu, 3 Mar 2016 16:48:55 +0200
> > > "Michael S. Tsirkin" wrote:
> > >
> > > > On Thu,
On Mon, 7 Mar 2016 14:22:38 +0200
"Michael S. Tsirkin" wrote:
> On Mon, Mar 07, 2016 at 01:16:48PM +0100, Igor Mammedov wrote:
> > On Thu, 3 Mar 2016 16:48:55 +0200
> > "Michael S. Tsirkin" wrote:
> >
> > > On Thu, Mar 03, 2016 at 10:05:31PM +0800, Xiao Guangrong wrote:
> > > >
> > > >
>
On Mon, Mar 07, 2016 at 01:16:48PM +0100, Igor Mammedov wrote:
> On Thu, 3 Mar 2016 16:48:55 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Thu, Mar 03, 2016 at 10:05:31PM +0800, Xiao Guangrong wrote:
> > >
> > >
> > > On 03/03/2016 09:29 PM, Michael S. Tsirkin wrote:
> > > >On Wed, Mar 02, 201
On Thu, 3 Mar 2016 16:48:55 +0200
"Michael S. Tsirkin" wrote:
> On Thu, Mar 03, 2016 at 10:05:31PM +0800, Xiao Guangrong wrote:
> >
> >
> > On 03/03/2016 09:29 PM, Michael S. Tsirkin wrote:
> > >On Wed, Mar 02, 2016 at 07:50:41PM +0800, Xiao Guangrong wrote:
> > >>As Igor suggested that we
On Thu, Mar 03, 2016 at 10:05:31PM +0800, Xiao Guangrong wrote:
>
>
> On 03/03/2016 09:29 PM, Michael S. Tsirkin wrote:
> >On Wed, Mar 02, 2016 at 07:50:41PM +0800, Xiao Guangrong wrote:
> >>As Igor suggested that we can report the BIOS patched operation region
> >>so that OSPM could see that par
On 03/03/2016 09:29 PM, Michael S. Tsirkin wrote:
On Wed, Mar 02, 2016 at 07:50:41PM +0800, Xiao Guangrong wrote:
As Igor suggested that we can report the BIOS patched operation region
so that OSPM could see that particular range is in use and be able to
notice conflicts if it happens some day
On Wed, Mar 02, 2016 at 07:50:41PM +0800, Xiao Guangrong wrote:
> As Igor suggested that we can report the BIOS patched operation region
> so that OSPM could see that particular range is in use and be able to
> notice conflicts if it happens some day
>
> Signed-off-by: Xiao Guangrong
This is res
As Igor suggested that we can report the BIOS patched operation region
so that OSPM could see that particular range is in use and be able to
notice conflicts if it happens some day
Signed-off-by: Xiao Guangrong
---
hw/acpi/nvdimm.c | 27 +++
1 file changed, 27 insertions(
11 matches
Mail list logo