On 11/20/2013 07:38 PM, Igor Mammedov wrote:
> - implements QEMU hardware part of memory hotplug protocol
> described at "docs/specs/acpi_mem_hotplug.txt"
> - handles only memory add notification event for now
>
> Signed-off-by: Igor Mammedov
> ---
> +0xa00:
> + read access:
> + [0x0-0x3
On Mon, 25 Nov 2013 15:31:22 +0100
Paolo Bonzini wrote:
> Il 25/11/2013 15:18, Igor Mammedov ha scritto:
> >> > For example on reset all slots could be disabled by the
> >> > ACPIHotpluggableDimmBus (even coldplugged ones), and scanned + enabled
> >> > by ASL.
> > memory devices are scanned by OS
Il 25/11/2013 15:18, Igor Mammedov ha scritto:
>> > For example on reset all slots could be disabled by the
>> > ACPIHotpluggableDimmBus (even coldplugged ones), and scanned + enabled
>> > by ASL.
> memory devices are scanned by OSPM during ACPI tables parsing and
> guest (can) use present devices
On Mon, 25 Nov 2013 14:45:15 +0100
Paolo Bonzini wrote:
> Il 25/11/2013 08:27, Markus Armbruster ha scritto:
> > "Michael S. Tsirkin" writes:
> >
> > [...]
> >> Here this made me think of the following question:
> >> should not memory available on boot be listed in CMOS?
> >> Let's assume new B
On Sun, 24 Nov 2013 12:58:57 +0200
"Michael S. Tsirkin" wrote:
> On Fri, Nov 22, 2013 at 06:14:46PM +0100, Igor Mammedov wrote:
> > On Thu, 21 Nov 2013 16:38:47 +0200
> > "Michael S. Tsirkin" wrote:
> >
> > > On Thu, Nov 21, 2013 at 03:21:37PM +0100, Igor Mammedov wrote:
> > > > On Thu, 21 Nov
Il 25/11/2013 08:27, Markus Armbruster ha scritto:
> "Michael S. Tsirkin" writes:
>
> [...]
>> Here this made me think of the following question:
>> should not memory available on boot be listed in CMOS?
>> Let's assume new BIOS gets interrupt telling it there's new memory.
>> It clears the inter
"Michael S. Tsirkin" writes:
[...]
> Here this made me think of the following question:
> should not memory available on boot be listed in CMOS?
> Let's assume new BIOS gets interrupt telling it there's new memory.
> It clears the interrupt and then system is reset.
>
> Will system after reset de
On Fri, Nov 22, 2013 at 06:14:46PM +0100, Igor Mammedov wrote:
> On Thu, 21 Nov 2013 16:38:47 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Thu, Nov 21, 2013 at 03:21:37PM +0100, Igor Mammedov wrote:
> > > On Thu, 21 Nov 2013 11:42:02 +0200
> > > "Michael S. Tsirkin" wrote:
> [...]
> > > > > +
On Thu, 21 Nov 2013 16:38:47 +0200
"Michael S. Tsirkin" wrote:
> On Thu, Nov 21, 2013 at 03:21:37PM +0100, Igor Mammedov wrote:
> > On Thu, 21 Nov 2013 11:42:02 +0200
> > "Michael S. Tsirkin" wrote:
[...]
> > > > + [0x14] highest memory hot-plug interface version supported by
> > > > QEMU
On Thu, Nov 21, 2013 at 03:21:37PM +0100, Igor Mammedov wrote:
> On Thu, 21 Nov 2013 11:42:02 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Thu, Nov 21, 2013 at 03:38:34AM +0100, Igor Mammedov wrote:
> > > - implements QEMU hardware part of memory hotplug protocol
> > > described at "docs/specs/
On Thu, 21 Nov 2013 11:42:02 +0200
"Michael S. Tsirkin" wrote:
> On Thu, Nov 21, 2013 at 03:38:34AM +0100, Igor Mammedov wrote:
> > - implements QEMU hardware part of memory hotplug protocol
> > described at "docs/specs/acpi_mem_hotplug.txt"
> > - handles only memory add notification event for
On Thu, Nov 21, 2013 at 03:38:34AM +0100, Igor Mammedov wrote:
> - implements QEMU hardware part of memory hotplug protocol
> described at "docs/specs/acpi_mem_hotplug.txt"
> - handles only memory add notification event for now
>
> Signed-off-by: Igor Mammedov
> ---
> docs/specs/acpi_mem_hotpl
- implements QEMU hardware part of memory hotplug protocol
described at "docs/specs/acpi_mem_hotplug.txt"
- handles only memory add notification event for now
Signed-off-by: Igor Mammedov
---
docs/specs/acpi_mem_hotplug.txt | 38 ++
hw/acpi/core.c | 144
13 matches
Mail list logo
